Crucible prd

Generate a stakeholder-facing PRD from a design doc. Use when you have a finalized design doc and need a non-technical product requirements document for archival or sharing. Triggers on /prd, 'generate PRD', 'write a PRD', 'product requirements'.

install

source · Clone the upstream repo

git clone https://github.com/raddue/crucible

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/raddue/crucible "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/prd" ~/.claude/skills/raddue-crucible-prd && rm -rf "$T"

manifest: skills/prd/SKILL.md

source content

PRD Generator

Overview

All subagent dispatches use disk-mediated dispatch. See

shared/dispatch-convention.md

for the full protocol.

Generates a Product Requirements Document (PRD) from a finalized design doc. The PRD reformats technical design decisions into stakeholder-friendly language — problem statement, user stories, requirements, scope, success metrics.

Announce at start: "I'm using the PRD skill to generate a product requirements document."

Core principle: The PRD derives everything from the design doc. It does not introduce new decisions or requirements — it translates existing technical decisions for a non-technical audience.

When to Use

After
```
/design
```
or
```
/build
```
Phase 1 completes — you have a finalized design doc
When a stakeholder asks for a PRD, product spec, or requirements document
When archiving a feature's requirements in Confluence, Jira, Notion, or similar

Input

The skill needs a design doc path. If not provided, it searches:

Check if the user specified a path:

/prd docs/plans/2026-03-23-my-feature-design.md

If no path: scan
```
docs/plans/
```
for the most recently modified
```
*-design.md
```
file
If no design docs found: inform user and stop

The Process

Read the design doc — verify it exists and has the expected structure (Overview, acceptance criteria, etc.)
Dispatch a Sonnet PRD Writer using the prompt template at
```
skills/build/prd-writer-prompt.md
```
- Input: full design doc text
- Output: PRD in standard format
Save to
```
docs/prds/YYYY-MM-DD-<topic>-prd.md
```
Commit:
```
docs: add PRD for [feature]
```
Report the file path to the user

PRD Structure

The generated PRD follows a fixed structure:

Problem Statement — what problem this solves, in plain language
User Stories / Use Cases — "As a [role], I want [goal] so that [benefit]"
Requirements — functional and non-functional, each a testable statement
Scope — what's included
Out of Scope — what was explicitly excluded
Success Metrics — measurable outcomes
Technical Notes — brief architectural context for stakeholders who want it
Dependencies — external systems, teams, or services

Integration

Called by:

crucible:build — Phase 1 Step 2.5 (after design finalized, before acceptance tests). Runs by default in feature mode, skipped in refactor mode.

Standalone usage:

```
/prd <design-doc-path>
```
— generate PRD from any design doc
```
/prd
```
(no args) — auto-detect most recent design doc

Prompt template:

skills/build/prd-writer-prompt.md

(shared with build pipeline)

Red Flags

Inventing requirements not in the design doc
Including code, file paths, or architecture diagrams in the PRD
Writing more than 2 pages — PRDs should be concise
Skipping sections rather than stating "Not specified in design"