open-spec-complete
Mark a change as done and sync the living specs.
Framework-agnostic: works whether you used temporary change artifacts, plan mode, TDD, or direct implementation.
The only obligation: specs/features/ must reflect what the system does now.
Input: Optionally specify a change name (if using specs/changes/<name>/). Otherwise the diff is inferred from git automatically.
Steps
-
Understand what changed
git diff HEAD --stat git statusRead the key changed files to understand which behaviors were added, modified, or removed.
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.
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.
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