software-design-doc

Generate a Software Design Description by providing your PRD or repository context to produce a canonical multi-file SDD set under docs/sdd/ and a dated gap report under .agent-doc-skills/sdd/gaps.

IEEE 1016 structure for software design documents provides a canonical format that maps requirements to architecture views, enforces formal design element definitions, and enables consistent architecture artifacts and governance.

Perform gap analysis and drift analysis by validating SDD structure and traceability, which produces dated gap and drift artifacts for review cycles under .agent-doc-skills/sdd/gaps.

Yes, you can use repository context to validate traceability in an SDD by mapping requirements to architecture views and enforcing canonical structure to generate gap and drift artifacts.

Maintain consistent architecture artifacts by drafting and validating IEEE 1016-inspired SDDs from PRD context, generating dated gap and drift artifacts for each review cycle to enforce governance.