trd

Generates a technical design document from an approved PRD via the architect agent.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill trd-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trd
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/trd
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill trd-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about trd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a technical design document from a PRD?▼

Run this step after a PRD exists and is approved. It invokes the architect agent with the PRD path, which writes specs/<slug>/trd.md from the TRD template and records architecture decision records in docs/adr/ when relevant.

What is the difference between a PRD and a TRD in spec-driven development?▼

A PRD defines what the product must do from a user and business perspective, while a TRD describes how it will be built technically, including architecture, ports, and trade-offs. The TRD is derived from the approved PRD.

Can I use a PRD file outside the specs/<slug>/ directory convention?▼

Yes. If you pass an existing file path as the argument, it is used directly as the PRD regardless of location. The convention is only needed for automatic slug-based detection.

What happens if no PRD exists when I run the TRD step?▼

The skill stops and tells you to run the PRD step first. It does not proceed without a PRD, since the technical design must be grounded in an approved product specification.

What if the architect agent is unavailable or cannot ask questions?▼

If the Agent tool is unavailable, you follow the architect agent's documented process directly. If the subagent returns questions as plain text, the orchestrator presents them to the user and relays answers back before finalizing the TRD.