Generate technical design documents with database schema, API routes, and frontend components.
npx skills add https://github.com/sdebaun/turnout-mvp --skill tdd-sdebaun
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/sdebaun/turnout-mvp/tree/main/.claude/skills/tdd Command: npx skills add https://github.com/sdebaun/turnout-mvp --skill tdd-sdebaun
This Skill generates comprehensive technical design documents (TDDs) to clearly outline the implementation details of a feature, ensuring alignment between product intent and engineering execution.
Use the tdd skill to write a technical design document for prd0001.
High-intent search queries and answers about installing and using this skill.
You generate a technical design document by feeding a product requirements document and contextual architecture information into the system. It outputs detailed implementation specifications covering database schemas, API routes, and frontend components to guide engineering execution.
A technical design document should include database schemas, API routes, and frontend components. It integrates contextual information from architecture docs and vision statements to align product intent with engineering execution.
Yes, you can use a product requirements document to automatically document database schemas and API routes. The system processes the PRD to generate a comprehensive technical design specifying the required data models and endpoints for implementation.
This technical design documentation approach relies on prior architecture docs, vision statements, or PRDs to inform the design. It integrates this contextual information to generate accurate database models, API endpoints, and frontend flows for implementation.
You need a technical design document before starting development on complex features like a user authentication system. It specifies the database models, API endpoints, and frontend flows required to ensure alignment between product intent and engineering execution.
PascaponeGenerate comprehensive Product Requirements Documents for software systems and AI features.
etylsarinImplement authentication, authorization, CSP, input validation, and RLS policies.
pacaplanVerify code implementation against OpenSpec change artifacts and design documents.
ToanPV90Document architectural decisions with ADRs capturing context and trade-offs.
