create-specification

To convert a PRD into a technical specification, you map high-level requirements into detailed, actionable tasks using structured prefixes like REQ, SEC, CON, GUD, and PAT. This process ensures functional, security, and design guidelines are clearly defined for implementation.

The Given-When-Then format structures acceptance criteria into testable statements. Given a specific context, When an action occurs, Then a specific outcome results. Enforcing this format ensures technical specifications have clear, verifiable conditions for development.

You categorize requirements in a technical design document by applying defined prefixes: REQ for functional requirements, SEC for security, CON for constraints, GUD for guidelines, and PAT for patterns. This systematically organizes specifications for stakeholders.

Yes, you can map technical specification elements directly to Maestro task fields. The specification generation process explicitly aligns requirement categories and acceptance criteria with Maestro fields like content, acceptance_criteria, and constraints.

The best way to structure acceptance criteria for implementable tasks is using the Given-When-Then format. This enforces clear, testable conditions within the technical specification template, covering overview, requirements, design, and testing sections.