wa:design-specs

You can generate API contracts and database schemas by providing a feature or epic description to a design specification generator. This tool runs a multi-phase workflow to produce endpoint definitions, request/response schemas, table designs, and migration plans.

Documenting non-functional requirements for a complex API is best handled by a complexity-tiered design spec generator. It captures quantified performance, scalability, security, reliability, and observability targets based on the feature's assessed complexity.

To create sequence diagrams for database schema migrations, use a design specification tool that adds them automatically for complex cases. It generates table designs, relationships, indexes, and sequence diagrams alongside the migration plans.

Yes, you can publish design specifications to Confluence directly. The tool writes versioned draft specs to local docs and optionally attempts a Confluence publish without blocking the workflow if the publish operation fails.

Yes, the design specification workflow requires plan mode to function. It uses plan mode to resolve development rigor and guide the multi-phase complexity assessment before generating the structured specification artifacts.