What problem does it solve? Turning a raw requirement description into a review-ready technical design document is error-prone: ambiguous terms get misinterpreted, complexity gets hidden in a single document, and designs drift from the existing codebase. This Skill structures the entire process so designs are split into a parent document plus sub-requirement documents, validated against the real code, and reviewed automatically before delivery. ## Core Features & Use Cases - Staged design workflow: Walks through requirement maturity assessment, semantic analysis, interaction mapping, requirement splitting into a dependency DAG, outline definition, chapter-by-chapter filling, and archival, with user confirmation required at each stage. - Multi-document structure by default: Splits complex requirements into a parent document (4 global chapters) plus per-sub-requirement documents with on-demand chapters, while simple changes can use a 14-chapter single-document fast track. - Automated review loop: After writing files, it runs design-review with up to 3 auto-fix rounds, then challenger second-round questioning and scenario rehearsal, with options to auto-fix, archive reports, or skip. - Use Case: Given a requirement like "simplify the import flow from 7 steps to 2", the Skill splits it into sub-requirements with a mermaid overview diagram, produces interface contracts with demo JSON responses and decision tables with rejected alternatives, then archives everything under the requirement directory and registers it via the req CLI. ## Quick Start Ask the AI to turn your requirement description into a technical design document, for example: use design-craft to create a design doc for adding idempotency to the task system.
