What problem does it solve?
It turns an Approved elicitation model plus Accepted epics and stories into a single, implementation-ready Software Requirements Specification (SRS) that teams can review and sign off—while preserving traceability and preventing accidental changes to already Accepted specifications.
Core Features & Use Cases
- Review-gated SRS compilation: Blocks compilation unless every Story under every Accepted Epic is Accepted, ensuring the SRS is a settled contract.
- IEEE 29148:2018 structure with partial-by-Epic scope: Generates Introduction, Overall Description, System Features (per epic), FR/NFR/CON consolidation, External Interfaces, Acceptance Criteria, and an always-rebuilt Traceability Matrix.
- Idempotent reruns with immutability rules: Regenerates freely when Pending; when Accepted, it keeps Sections 1–8 unchanged and refreshes only Traceability/Revision notes to reflect upstream changes.
Quick Start
Run the create-srs skill to compile artifacts/04-srs/srs.md from the approved elicitation document and the Accepted epic/story set.