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 so architecture, behavior, and domain knowledge stay current and traceable to requirements. ## Core Features & Use Cases - Structured Doc Generation: Creates domain.md, technical-spec.md, behavior-spec.md, a design changelog, and a reference/ directory with language-specific material kept strictly separate from normative text. - Stable Section-ID Registry: Assigns permanent D-###, S-###, B-###, and R-### section IDs tracked in traceability.json, so sections are never renumbered across regenerations. - Spec Traceability: Every section carries a traceability footer linking to FR-### requirement IDs from the project spec, plus a human-readable mirror table in technical-spec.md. - Use Case: After a development phase changes several modules, run the sync mode to update only the affected design-doc sections, append a design-changelog entry, and keep docs aligned with the current spec without touching source code. ## Quick Start Ask the architect to run the design-docs mode with a system description, for example: generate design docs for the document ingestion pipeline into the docs directory.
