prd

Generates a Product Requirements Document for a new feature via the product-design agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable Product Requirements Document is slow and inconsistent when done ad hoc. This Skill runs stage 1 of the SDD pipeline, producing a standardized PRD at specs/<slug>/prd.md with sequential numbering, optional UI wireframes, and timing logs. ## Core Features & Use Cases - PRD Generation: Invokes the product-design agent to write a PRD from a free-text request or an existing requirements file, using the specs/_template/prd.template.md structure. - UI Wireframe Exploration: For features with UI, offers 2-3 low-fidelity wireframe options via the design skill, persists the .dc.html sources under specs/<slug>/wireframes/, and records design-system decisions in docs/DESIGN-SYSTEM.md. - Pipeline Governance: Assigns sequential spec numbers, logs invocation duration to timing-log.md, relays subagent questions to the user, and iterates on feedback until explicit approval. - Use Case: Describe a new dashboard feature in plain language; the Skill asks about wireframes, generates the PRD, summarizes it for approval, and hands off to the /btt-sdd:trd stage. ## Quick Start Ask the assistant to create a PRD for the new feature you want to build, optionally pointing to an existing requirements file.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a PRD from a feature idea?▼

Describe the feature in free text or pass a path to an existing requirements file. The Skill assigns the next sequential spec number, invokes the product-design agent, and saves the PRD to specs/<slug>/prd.md using the standard template.

How do I get wireframes before writing a PRD?▼

If the feature includes UI, the Skill offers 2-3 low-fidelity wireframe options via the design skill before writing user stories. Chosen wireframe sources are saved under specs/<slug>/wireframes/ so they remain available after the Artifact expires.

Can I use an existing requirements document as input?▼

Yes. Pass the file path as the argument and the Skill reads its content as the basis for the PRD. It does not require any prior artifact from the pipeline to start.

What happens if the product-design agent is unavailable?▼

The Skill instructs the orchestrator to follow the same product-design process directly with the same rigor. The wireframe offer step still applies since it depends on tools the agent alone lacks.

What comes after the PRD is approved?▼

After explicit user approval, the next stage is /btt-sdd:trd, where the architect agent produces the Technical Requirements Document. The PRD and timing log stay uncommitted until the implementation stage creates the first branch.