Menu
Show PRD build orchestration status
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Decompose a PRD into parallel work units and build them with independent agents
Run /prd-build over multiple PRDs with full worktree lifecycle (create, dispatch, FF-merge, cleanup). Single-command dispatch from one session — sequential or parallel.
Evaluate an MCP tool's agentic usability via parallel test scenarios plus a meta-reflection pass, producing a scored improvement report
Cancel or pause a PRD build run
Resume a paused or interrupted PRD build run
Run diverge → converge → premortem pipeline to produce a risk-annotated PRD
| name | prd-build-status |
| description | Show PRD build orchestration status |
| argument-hint | |
| allowed-tools | ["Read"] |
Read the state file and present a clear status report.
if [ -f .claude/prd-build.state.json ]; then
cat .claude/prd-build.state.json
else
echo "NO_STATE_FILE"
fi
If NO_STATE_FILE: tell the user there's no active PRD build run. Suggest /prd-build <prd-path> to start one.
Otherwise, also read .claude/prd-build-artifacts/dag.json with the Read tool to get unit-level detail.
PRD Build Status: <status>
Pass: <current>/<max> | Started: <time>
Progress:
Layer 0: [landed] unit-a, [landed] unit-b
Layer 1: [active] unit-c (implement), [pending] unit-d
Layer 2: [pending] unit-e
Summary: X/Y units landed | Z active | W pending | E evicted
Use status indicators:
landed — merged to integration branchactive — agent currently working (show pipeline stage if available)passed — done, waiting in merge queuepending — not yet startedevicted — merge failed, awaiting retryfailed — permanently failedAlso read and show the last 10 lines of .claude/prd-build.log.md as recent activity.