tdd-design-detail

Converting a high-level design into a detailed design involves mapping entities and behaviors to modules, interfaces, and test boundaries. This Skill generates a reproducible detailed-design.md artifact from your existing design.md file.

Structuring module interfaces and test boundaries is best handled by generating a detailed-design document that translates high-level architecture into concrete implementation plans, ensuring reproducible mapping between entities and modules.

Yes, an existing design.md file is required. The Skill performs collaborative preflight checks, reads your current high-level design, and outputs the detailed design to docs/tdd-designs/<design-name>/detailed-design.md.

Detailed design generation handles implementation planning by validating the existing design and producing an executable implementation plan alongside the detailed-design.md, covering module structure, interfaces, and data flow.

Yes, you can use this approach for collaborative architecture validation. The process includes preflight checks and design validation to guide team planning before outputting the final detailed design artifact.

A limitation of generating a detailed design is its strict dependency on a pre-existing high-level design.md file; without a valid initial design, the Skill cannot map modules or generate the implementation plan.