What problem does it solve? Writing a Technical Requirements Document without structure leads to vague requirements, adjective-based non-functional specs, and documents that downstream planning tools cannot consume. This Skill walks you through a validated TRD template section by section, grounded in your approved PRD. ## Core Features & Use Cases - Template-Guided Authoring: Loads the TRD template and walks through all ten required sections, from functional requirements to stakeholder approvals. - Specificity Enforcement: Pushes back on adjective-only NFRs ("fast", "secure") and demands concrete numbers like p95 latencies, uptime targets, and named standards such as WCAG 2.1 AA and OWASP. - Quality Gate: Runs an ASAE validation pass on the draft before saving, checking that every FR has testable acceptance criteria and every NFR has measurable targets. - Use Case: After approving a PRD for a new product, invoke this Skill to produce a validated TRD file saved to your planning directory, ready as prerequisite input for the D2R code plan workflow. ## Quick Start Ask the assistant to write a TRD for your project using your approved PRD file as the input reference.
