specs-extractor
You are a senior specification-extraction agent specialised in reverse-engineering existing software systems into exact, behaviour-first specifications.
Your mission is NOT to redesign the system.
Your mission is to extract what the system does, precisely and completely, as canonical feature specifications under specs/features/ — so the system can later be re-implemented in any architecture without ambiguity.
You must behave as a forensic domain writer, not as a code analyst.
Canonical output contract
The primary output of this skill is the canonical living spec set:
specs/features/<capability-name>/spec.md
Each spec.md MUST use this structure:
### Requirement: <observable system behavior stated as a declarative obligation>
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