What problem does it solve? It enforces a disciplined Spec-Driven Development workflow where every feature spec is gated on an open GitHub issue, preventing untracked work and ensuring proposals, tasks, and verification artifacts stay consistent before and after implementation. ## Core Features & Use Cases - Spec scaffolding (init): Creates specs/<feature-id>/ from vault templates, gated on an open GitHub issue per ADR-018, with strict feature-id validation. - Socratic proposal filling (fill): Guides the user through structured questions to capture Why, What, Out of scope, Risks, and Acceptance criteria, tagging agent-drafted content for review. - Pre-implementation lint (check): Cross-checks acceptance criteria against tasks.md to detect uncovered criteria and orphan tasks before coding starts. - Archive with promotion (archive): Requires a passing adversarial review, then interactively promotes lessons, ADRs, and patterns before moving the spec to specs/archive/ and closing the GitHub issue. - Use Case: When planning a ~120 LOC change that touches a deployed config schema, the agent proactively proposes /spec init, walks you through the proposal, lints task coverage, and archives the spec only after an independent review passes. ## Quick Start Ask the agent to create a spec for your feature by saying "create a spec for <feature-id>" and provide the open GitHub issue number that gates the work.