spec-kit-clarify
Resolve ambiguities in a feature spec through focused, sequential questioning.
Input: Optionally specify a change name. If omitted, infer from context or ask.
Steps
-
Select the change
Auto-select if only one directory exists under
specs/changes/. Otherwise ask. -
Load
specs/changes/<name>/spec.mdIf it does not exist, prompt the user to use the
spec-kit-specifyskill first. -
Scan for ambiguities
Examine the spec for issues across these categories (in priority order):
- Functional scope — unclear boundaries or behavior
- Data models — undefined entities, states, or transitions
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-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.
35