What problem does it solve? Teams often jump from requirements straight into code without a coherent system design, leaving components untraceable to the requirements they serve and design docs that drift out of sync. This Skill turns a requirements spec into a living architecture document where every component traces back to a specific FR/NFR. ## Core Features & Use Cases - Traceable system design: Generates docs/ARCHITECTURE.md with components, interfaces, data flow, and a bidirectional FR/NFR traceability table checked in both directions. - Living document revisions: Edits an existing architecture doc in place rather than appending, designing only gaps so unchanged components are not redesigned. - Built-in gates: Enforces an encryption check before writing, a hard gate against unjustified design decisions, and a conditional security review offer when the design exposes a network or sensitive-data surface. - Use Case: After running /requirements on a new feature, invoke /architecture to produce a mermaid system diagram, component list, and traceability table, then hand off to /write-plan for task breakdown. ## Quick Start Run /architecture with a short feature note after your docs/REQUIREMENTS.md exists to generate or revise the system design document.
