long-task-design

To generate a technical design document from an approved SRS, you need a tool that translates software requirements into implementation plans. This skill produces comprehensive design artifacts covering architecture, data models, and APIs by enforcing a structured, section-by-section design approval process.

The best way to design system architecture before coding is to use a design-first methodology that bridges requirements and implementation. This approach proposes and refines component interactions and technology stack choices, ensuring alignment with project requirements and preventing premature coding.

Yes, you can create data models and API endpoints directly from user-centered design documents. The skill processes approved UCD and SRS files to generate detailed technical designs, mapping user needs and software requirements directly to database schemas and interface specifications.

Detailed design documents handle non-functional requirements by ensuring the proposed system architecture and testing strategies explicitly align with them. This skill enforces strict design validation against NFRs during the section-by-section approval phase to guarantee the final design meets all constraints.

Yes, you need an approved Software Requirements Specification to start system architecture design. This skill requires a finalized SRS as input to accurately propose implementation approaches and generate detailed design artifacts, ensuring the technical design directly reflects the defined software requirements.