| name | plan |
| description | Plan an OpenSpec change by generating proposal artifacts, running one holistic planning review, and iterating until blocker and concern findings are resolved. |
| disable-model-invocation | true |
plan
Plan an OpenSpec change. Generate planning artifacts, review them, and iterate until blockers and concerns are resolved.
Inputs
- Change name
- User intent
- Existing conversation context
- Existing OpenSpec artifacts, if any
Workflow
- Resolve the change name from input or ask for it.
- Invoke the planner subagent. The prompt MUST start with:
/skill:openspec-propose <change-name>
- After proposal, specs, design, and tasks exist, run one planning review as a
reviewer subagent. The prompt MUST start with:
/skill:review-plan <change-name>
- Collect all review findings after the review completes.
- If findings contain only suggestions or no issues, stop.
- If findings contain blockers or concerns, update only the targeted artifact using its OpenSpec instructions and dependency artifacts; do not rerun full proposal generation over all artifacts.
- If a finding identifies an upstream artifact problem, update that upstream artifact and rerun the planning review after the affected artifacts are coherent again.
- If a finding requires a product, scope, or design decision that is not in the artifacts, ask the user instead of guessing.
- Repeat review → targeted fixes until blockers and concerns are resolved.
- Stop after at most 5 review/fix iterations.
- If unresolved blockers or concerns remain after 5 iterations, report them and ask the user for a decision.
Review loop rules
- Blockers must be fixed before planning is complete.
- Concerns must be fixed or explicitly accepted by the user.
- Suggestions do not block planning completion.
- Deduplicate findings before sending them back for artifact-specific fixes.
- Preserve reviewer wording for target artifact, upstream artifact, decision needs, evidence, impact, and recommended fix.
- Do not hide unresolved findings.
Completion
Planning is complete when:
- proposal exists
- specs exist
- design exists
- tasks exist
- planning review reports no blockers
- planning review reports no unresolved concerns
Return:
- artifacts created or updated
- review status
- remaining suggestions
- whether the change is ready for
implement
Guardrails
- Do not write application code.
- Do not perform implementation.
- Do not archive.
- Do not commit, push, create PRs, deploy, or run release steps.
