What problem does it solve? Teams that adopted spec-driven development after writing code often have working features with no corresponding speckit specifications, leaving no documented design intent for future maintenance or audits. ## Core Features & Use Cases - Reverse-engineered spec generation: Analyzes existing source files, tests, and docs to produce spec.md, plan.md, data-model.md, contracts/, research.md, and quickstart.md inside a numbered specs/ directory. - Feature discovery with confirmation: Builds a feature map of core abstractions, provider implementations, models, and tests, then waits for user approval before generating artifacts. - Optional tasks.md: Skips task checklist generation by default; with the --tasks flag it emits a fully checked-off task breakdown mapped to real files. - Use Case: A .NET library ships a streaming chat feature without specs; run the skill with the feature name to generate a complete speckit bundle traceable to the actual code. ## Quick Start Ask the assistant to run /speckit-retrospec with a feature name like "streaming chat" to generate the speckit specification bundle from the existing implementation.
