ai-ready-product-workflow-v2: Command for Claude Code

/po-pipeline

Run the full PO pipeline for a feature: Brief → PRD → USM → USL → USD → UAT.

Usage

/po-pipeline [feature-name] [brief or description]

If feature-name is omitted, ask for it before starting. If a brief is provided inline, use it directly. If not, ask the user to paste or describe the feature.

---

What This Command Does

Executes the 5-stage PO artifact pipeline in sequence for a single feature. Each stage produces a traceable artifact stored in features/{feature-name}/po/.

Stage	Skill	Input	Output
1	po-brief-to-prd	Feature brief	prd.md
2	po-prd-to-usm	prd.md	usm.md
3	po-usm-to-usl	usm.md	usl.md
4	po-usl-to-usd	usl.md	usd/ST-XXX.md per story
5	po-usd-to-uat	usd/ST-XXX.md	uat/ST-XXX.md per story

---

Execution Steps

Step 0 — Setup

1. Confirm the feature name (use $ARGUMENTS if provided, otherwise ask)
2. Create the feature folder structure:

   features/{feature-name}/
   ├── po/
   │   ├── usd/
   │   └── uat/
   ├── design/
   ├── pm/
   └── code/
   

3. If a brief already exists at features/{feature-name}/brief.md, read it. Otherwise use the brief from $ARGUMENTS or ask the user.

Step 1 — PRD (po-brief-to-prd)

• Read the brief
• Activate po-brief-to-prd skill
• Generate features/{feature-name}/po/prd.md
• Pause and show the PRD to the user
• Ask: "PRD looks good? Proceed to User Story Map, or revise first?"

Step 2 — USM (po-prd-to-usm)

• Read prd.md
• Activate po-prd-to-usm skill
• Generate features/{feature-name}/po/usm.md
• Show the user story map to the user
• Proceed automatically to Step 3 (unless user says stop)

Step 3 — USL (po-usm-to-usl)

• Read usm.md
• Activate po-usm-to-usl skill
• Generate features/{feature-name}/po/usl.md with MoSCoW prioritization
• Show the story list (count of Must/Should/Could/Won't)
• Ask: "Proceed to write acceptance criteria for all Must-Have stories?"