What problem does it solve? It turns an approved Product Requirements Document into a concrete Technical Requirements Document, bridging the gap between product intent and implementation in a spec-driven development pipeline. ## Core Features & Use Cases - TRD Generation: Invokes the architect agent to produce specs/<slug>/trd.md from specs/<slug>/prd.md using a template, recording ADRs in docs/adr/ when relevant. - Flexible Input Resolution: Accepts a direct PRD file path, a slug, or auto-detects the single spec lacking a TRD, so it works outside strict directory conventions. - Orchestrated Q&A and Timing: Relays architect questions to the user when the subagent runs asynchronously, and logs invocation duration to specs/<slug>/timing-log.md. - Use Case: After approving a PRD for a new billing feature, run this step to get an architecture proposal with defined ports and trade-offs, review it, request adjustments, and approve before implementation begins. ## Quick Start Ask the assistant to run the trd step on the approved PRD for your feature so the architect agent produces the technical design document for your review.