What problem does it solve? Turning a rough feature idea into code without a written design leads to drift, missing invariants, and unbounded scope. This Skill converts requirements into a numbered, cross-linked, dependency-ordered spec set under ./specs that serves as the contract between intent and code. ## Core Features & Use Cases - Structured spec generation: Produces a PRD, data model, per-component designs, cross-cutting specs (security, performance, testing), glossary, and a key-decisions log, sized to the complexity of the system. - Dual planning documents: Writes a stakeholder-facing milestone roadmap (90-roadmap.md) and an engineer-facing dependency-ordered implementation plan (91-impl-plan.md) that pair 1:1 but are organized differently. - Prior-art grounding: Cross-references research memos in ./docs/research, vendored code in ./vendors, and encodes AGENTS.md engineering norms directly into design decisions. - Use Case: A team wants to build an observability SDK. The Skill produces an index, PRD with measurable goals, component designs with ASCII architecture diagrams, a phased roadmap with exit criteria, and a key-decisions log before any code is written. ## Quick Start Use the spec skill to turn my feature idea into a dependency-ordered spec set with a PRD, roadmap, and implementation plan under ./specs.
