What problem does it solve? Keeping design documentation consistent with evolving code and specs is tedious and error-prone. This Skill automates the generation and synchronization of structured, language-agnostic design docs (domain.md, technical-spec.md, behavior-spec.md) so documentation never drifts from the authoritative spec. ## Core Features & Use Cases - Structured Doc Generation: Creates a fixed set of design docs (domain, technical-spec, behavior-spec, design-changelog, reference/) with stable section IDs (D-###, S-###, B-###, R-###) that are never renumbered. - Spec Traceability: Maintains a machine-readable traceability.json registry mapping every doc section to spec FR IDs, invariants, and code anchors, plus a human-readable mirror table. - Sync Mode: Updates only affected sections when code or specs change, preserving existing IDs and appending entries to a design changelog. - Use Case: After completing a development phase, trigger a sync so the design docs reflect the latest diff, with drift detection flagging stale sections automatically. ## Quick Start Ask the architect to run the design-docs command to generate fresh design documentation for the project from the current spec.
