spec-kit-specify
Create a feature specification from a natural language description.
Input: Feature description. If not provided, ask the user what they want to build.
Steps
-
Collect the feature description
If input is missing or vague, ask:
"What feature do you want to specify? Describe what it should do and why."
Derive a kebab-case name (e.g., "add user authentication" →
user-auth). -
Create the change directory
Create
specs/changes/<name>/.specs/changes/is gitignored. Onlyspecs/features/is canonical and versioned.
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-plan
Create a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
36spec-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