What problem does it solve? Writing consistent, traceable detailed design documents for every screen or feature of a system is slow and error-prone, especially when each document must include sequence diagrams, error flows, and traceability back to requirements. This Skill guides an interactive workflow that synthesizes existing specs, prototypes, tech-stack decisions, and acceptance criteria into per-screen conceptual design documents. ## Core Features & Use Cases - Per-screen Detailed Design Documents: Creates or updates one Markdown file per screen/feature under docs/02-design/02-technical/detailed-design/, each containing at least one mermaid sequenceDiagram. - AI Component Rule Enforcement: For screens involving AI components (TOR Parser, Design Analyzer, Test Generator, Document Writer), it enforces rules such as JSON-only AI output, source references, and a mandatory human review gate before any data is persisted. - Interactive Scope and Detail-Level Selection: Uses structured questions with at least three options (with pros and cons) to confirm scope, update mode (create, patch, or rewrite), and diagram detail level before writing any file. - Use Case: A system analyst asks to produce detailed designs for the MVP screens; the Skill reads the screen specs, backlog, system design document, and prototypes, confirms the plan, then delegates file writing to a dedicated sub agent. ## Quick Start Ask the assistant to create detailed design documents with sequence diagrams for the MVP screens based on the existing specs and prototypes.
