spec-design

To generate architecture diagrams from requirements, the system translates requirements.md into Mermaid diagrams, ensuring strict alignment with steering and tech constraints while capturing any technical trade-offs or blockers.

Yes, you need a requirements.md file placed in the .claude/specs/ directory, as the workflow relies on existing requirements and steering constraints to produce the Prisma schema and OpenAPI definitions.

The generated design.md details context, architecture diagrams, data models, API contracts, error taxonomy, observability, security, and alternatives, providing a complete architectural blueprint for your project.

Yes, spec-design works with Prisma and OpenAPI by taking your project requirements and translating them directly into Prisma data models and OpenAPI API contracts within the output design document.

To ensure generated data models align with steering constraints, the workflow checks your requirements against steering/tech.md, capturing blockers and trade-offs to maintain strict architectural alignment throughout the design process.