spec-kit-plan
Create a technical implementation plan from a feature specification.
Input: Optionally specify a change name. If omitted, infer from context or ask.
Steps
-
Select the change and load artifacts
Load
specs/changes/<name>/spec.md. If it does not exist, prompt to use thespec-kit-specifyskill first.Also load
specs/features/relevant to the area being changed. -
Research unknowns
If the spec contains unresolved
[NEEDS CLARIFICATION]markers, pause and suggest using thespec-kit-clarifyskill first unless the user explicitly wants to proceed. -
Write
specs/changes/<name>/plan.mdStructure:
More from aircury/ai-framework
open-spec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
40open-spec-apply
Implement tasks from a working change. Use when the user wants to start implementing, continue implementation, or work through planned tasks.
38open-spec-propose
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
38open-spec-complete
Mark a change as complete. Syncs specs/features/ to reflect current system behavior, then cleans up optional workflow artifacts. Framework-agnostic and independent of any external spec tool.
38spec-kit-specify
Create a feature specification from a user description. Focuses on WHAT and WHY, never HOW. Use at the start of a spec-kit workflow.
35spec-kit-clarify
Resolve ambiguities in a feature spec through targeted Q&A. Run after spec-kit-specify when open questions remain. Updates spec.md incrementally.
35