OpenSpec Propose Skill
When to Invoke
Automatically activate when user:
- Says "Fix this bug", "Small change", "Quick feature"
- Asks "Simple fix for [issue]", "Minor update to [component]"
- Mentions "bug fix", "small improvement", "quick change"
- Has a Level 0-1 scoped change (small, low risk, no major unknowns)
- Uses words like: bug, fix, small, quick, simple, minor, lightweight
Specific trigger phrases:
- "Fix this bug: [description]"
- "Small change to [component]"
- "Quick feature: [simple feature]"
- "Simple fix for [issue]"
- "Minor update: [description]"
- "Lightweight change proposal"
Prerequisites:
- Change is Level 0-1 (small, well-defined)
- No major unknowns or architectural changes
- Existing codebase (not greenfield project)
Do NOT invoke when:
- Complex feature requiring PRD (use BMAD instead)
- Architectural changes needed (use bmad-architecture-design)
- Multiple teams coordination (use BMAD)
- Level 2+ complexity (escalate to BMAD)
- Greenfield project (use BMAD workflow)
Auto-escalate to BMAD when:
- Scope grows beyond Level 1
- Major unknowns emerge
- Requires cross-team coordination
Mission
Capture small change requests or bug fixes and translate them into concise proposals and task outlines without invoking the full BMAD workflow.
Inputs Required
- change_request: description of the existing behavior and desired adjustment
- impact_surface: files, services, or user flows likely affected
- constraints: timeline, risk, or approvals that bound the solution
Outputs
proposal.md summarizing problem, desired behavior, and acceptance signals (template: assets/proposal-template.md.template)tasks.md listing actionable steps sized for rapid implementation (template: assets/tasks-template.md.template)specs/spec-delta.md capturing ADDED/MODIFIED/REMOVED requirements (template: assets/spec-delta-template.md.template)- Optional
design.md scaffolded when deeper technical notes are required
scripts/scaffold_change.py creates this structure in openspec/changes/<change-id>/ using the templates above.
Process
- Validate Level 0-1 scope using
CHECKLIST.md.
- Run
scripts/scaffold_change.py <change-id> to create the workspace under openspec/changes/.
- Clarify current vs. target behavior and record feasibility notes in
proposal.md.
- Draft
tasks.md and populate specs/spec-delta.md using the templates in assets/.
- Highlight dependencies, approvals, and risks, then hand off for review or implementation scheduling.
Quality Gates
Ensure checklist items pass before finalizing. Escalate to BMAD if scope exceeds Level 1 or introduces major unknowns.
Error Handling
- If information is insufficient, ask for missing context (screenshots, logs, reproduction steps).
- When risks are high or ambiguity remains, recommend migrating to BMAD discovery-analysis.
1---2name: openspec-change-proposal3description: Creates lightweight proposals for L0-1 work.4---5
6# OpenSpec Propose Skill
7
8## When to Invoke
9
10**Automatically activate when user:**
11- Says "Fix this bug", "Small change", "Quick feature"
12- Asks "Simple fix for [issue]", "Minor update to [component]"
13- Mentions "bug fix", "small improvement", "quick change"
14- Has a Level 0-1 scoped change (small, low risk, no major unknowns)
15- Uses words like: bug, fix, small, quick, simple, minor, lightweight
16
17**Specific trigger phrases:**
18- "Fix this bug: [description]"
19- "Small change to [component]"
20- "Quick feature: [simple feature]"
21- "Simple fix for [issue]"
22- "Minor update: [description]"
23- "Lightweight change proposal"
24
25**Prerequisites:**
26- Change is Level 0-1 (small, well-defined)
27- No major unknowns or architectural changes
28- Existing codebase (not greenfield project)
29
30**Do NOT invoke when:**
31- Complex feature requiring PRD (use BMAD instead)
32- Architectural changes needed (use bmad-architecture-design)
33- Multiple teams coordination (use BMAD)
34- Level 2+ complexity (escalate to BMAD)
35- Greenfield project (use BMAD workflow)
36
37**Auto-escalate to BMAD when:**
38- Scope grows beyond Level 1
39- Major unknowns emerge
40- Requires cross-team coordination
41
42## Mission
43Capture small change requests or bug fixes and translate them into concise proposals and task outlines without invoking the full BMAD workflow.
44
45## Inputs Required
46- change_request: description of the existing behavior and desired adjustment
47- impact_surface: files, services, or user flows likely affected
48- constraints: timeline, risk, or approvals that bound the solution
49
50## Outputs
51- `proposal.md` summarizing problem, desired behavior, and acceptance signals (template: `assets/proposal-template.md.template`)
52- `tasks.md` listing actionable steps sized for rapid implementation (template: `assets/tasks-template.md.template`)
53- `specs/spec-delta.md` capturing ADDED/MODIFIED/REMOVED requirements (template: `assets/spec-delta-template.md.template`)
54- Optional `design.md` scaffolded when deeper technical notes are required
55
56`scripts/scaffold_change.py` creates this structure in `openspec/changes/<change-id>/` using the templates above.
57
58## Process
591. Validate Level 0-1 scope using `CHECKLIST.md`.
602. Run `scripts/scaffold_change.py <change-id>` to create the workspace under `openspec/changes/`.
613. Clarify current vs. target behavior and record feasibility notes in `proposal.md`.
624. Draft `tasks.md` and populate `specs/spec-delta.md` using the templates in `assets/`.
635. Highlight dependencies, approvals, and risks, then hand off for review or implementation scheduling.
64
65## Quality Gates
66Ensure checklist items pass before finalizing. Escalate to BMAD if scope exceeds Level 1 or introduces major unknowns.
67
68## Error Handling
69- If information is insufficient, ask for missing context (screenshots, logs, reproduction steps).
70- When risks are high or ambiguity remains, recommend migrating to BMAD discovery-analysis.
majiayu000