tech-spec-architect

To generate a technical design document from a PRD, use an automated skill that transforms product requirements through a Socratic interview into machine-readable TDDs featuring Mermaid diagrams, JSON Schema, and OpenAPI specifications for AI and human consumption.

The best way to structure a TDD for AI coding assistants is to use modern minimalist principles with machine-readable formats like Mermaid diagrams, JSON Schema for data models, and OpenAPI for API specifications, ensuring clear dual human-AI consumption.

A Socratic interview clarifies technical design requirements by engaging the user in a dialogue to resolve ambiguities in the PRD and identify architectural anti-patterns or red flags before finalizing the machine-readable TDD output.

Yes, you can use Mermaid diagrams and OpenAPI specifications in automated TDD generation to structure visual flows and API contracts, alongside JSON Schema for data models, creating a comprehensive machine-readable technical design document.

You need a machine-readable technical design document when converting raw PRDs into structured implementation guides, ensuring architectural consistency and clarity for both human developers and AI coding assistants collaborating on the codebase.

A limitation of generating TDDs from product requirements is that the output quality depends heavily on the initial PRD clarity, requiring a Socratic interview phase to identify architectural red flags and resolve ambiguities before producing the final specifications.