PRD Backlog Conductor
A superpowers-based requirements manager: brainstorm and backlog requirements as cards, schedule by ▎ dependency/conflict, and dispatch confirmed ones to background subagents in isolated worktrees (plan → TDD → verify ▎ → accept) without blocking your session.
wdp-prd-en — Requirements Management
A superpowers-based requirements manager that decouples discussion from implementation. Brainstorm new requirements into cards at any time; confirmed ones are implemented in parallel by background subagents without blocking the main session.
When to Use
- Discuss/record a new requirement (not implemented immediately) →
/wdp-prd-new - View the backlog / scheduling state →
/wdp-prdor/wdp-prd-list - Confirm a requirement as dispatchable →
/wdp-prd-confirm <id> - Dispatch implementation →
/wdp-prd-dispatch - Accept a completed requirement →
/wdp-prd-accept <id> - Edit a card →
/wdp-prd-update <id>
Storage Model
- Global root:
~/.wdp/prd/(override with thePRD_ROOTenvironment variable). - Per-project subdirectory:
<PRD_ROOT>/<project-slug>/, containing:backlog/R-###.mdrequirement cardsexecution-plan.mdscheduling viewplans/implementation-plan archive
- Bridge: a
.wdp-prdfile in the project root whose content is the absolute path of that project's global root (i.e.<PRD_ROOT>/<slug>/). Read it before every command operation.
Initialization
If <cwd>/.wdp-prd does not exist:
- Ask for the project name (slug, lowercase hyphenated).
- Create
<PRD_ROOT>/<slug>/(withbacklog/,plans/) and an emptyexecution-plan.md, and createdocs/superpowers/specs/inside the project. - Write
.wdp-prdcontaining the absolute path of the global root. - Report that initialization is complete.
State Machine
draft → confirmed → in-progress → needs-review → accepted → done
Also: blocked (unmet dependency / subagent failure), cancelled.
Scheduling Rules
Compute a status report over all cards, with two rules (no topological sort in the MVP):
- A dependency in
depends_onthat is still notdone→⏳ waiting for R-00X(dependencies that arecancelledcount as satisfied and do not block). - An entry in
conflicts_withthat isin-progress→⚠ conflicts with R-00X(dev in progress); wait for it or let the user decide.
Before computing, check the depends_on relations: if there is a cycle, report it (R-003↔R-004), mark the involved cards blocked, and do not dispatch; if a dependency id does not exist, report dependency R-999 does not exist; check depends_on and do not dispatch. Cards with a missing dependency go into the ⏳ blocked list with dependency missing noted in parentheses.
The parentheses in the blocking hint show the dependency card's actual current state (e.g. confirmed / in-progress / cancelled).
Immediately dispatchable = status==confirmed + all dependencies satisfied + no conflict with in-progress + in-progress count < concurrency cap.
Concurrency cap defaults to 2, configurable via the PRD_MAX_CONCURRENT environment variable. When exceeded, report concurrency cap reached; accept what's in hand first.
Same-batch constraint: the batch the user picks must be pairwise non-conflicting; if they pick a pair that lists each other in conflicts_with, force picking only one; each batch is at most PRD_MAX_CONCURRENT − current in-progress cards.
Report format:
▶ ready to dispatch in parallel [R-001, R-002]
⏳ blocked by dependency R-005 → wait for R-002(dev in progress)
⚠ conflicts with in-progress task R-003 ↔ R-004(dev in progress)
execution-plan.md
Rewritten by Claude after every status change / dispatch / acceptance (based on the current state of all cards: needs-review/accepted/done cards naturally leave the in-progress / ready / blocked / conflict lists and no longer appear):
# Execution Plan (auto-generated, do not edit by hand)
Updated: YYYY-MM-DD
in-progress: [R-001, R-002]
ready: []
blocked: R-005 → wait for R-002
conflicts: []
Commands
/wdp-prd — Main entry
- Read all cards, output a backlog summary table (id/title/status/priority/dependencies).
- Compute and output the current scheduling status report per the Scheduling Rules (ready / blocked by dependency / conflicts / concurrency-cap hint; format as above).
- Prompt the available
/wdp-prd-*commands.
/wdp-prd-list — List
Output a backlog summary table sorted by priority from high to low, then by created ascending within the same priority. If there are no cards, state that explicitly.
/wdp-prd-update — Edit a card
- Locate the card (if missing, report an error and list recent ids).
- Ask which fields to change (status/priority/depends_on/conflicts_with/title).
- Validate values: status must be in the state-machine set; priority must be high/medium/low.
- Update the fields, set
updatedto today, keepcreatedunchanged. - Rewrite
execution-plan.md(if affected).
/wdp-prd-confirm — Confirm a requirement
- The card exists and status==draft; otherwise report an error stating the current status.
- On confirmation status→confirmed,
updatedis refreshed. - Rewrite
execution-plan.md.
/wdp-prd-dispatch — Dispatch
- Produce the scheduling status report (rules in Scheduling Rules).
- The user picks a batch to dispatch now (pairwise non-conflicting; when the concurrency cap is exceeded, prompt to accept first).
- Spawn one background subagent per requirement, executed in a git-worktree-isolated branch:
superpowers:writing-plans→superpowers:test-driven-development→ development →superpowers:verification-before-completion; at dispatch time, move the card → in-progress, refreshupdated, and rewriteexecution-plan.md(so the card counts as in-progress for the subagent's entire run); when the subagent produces an implementation plan, archive it to<pointer>/plans/<id>.md. - The subagent returns a report: which files it changed, which tests it ran, results, leftover issues.
- When the subagent finishes: move the card → needs-review, and prompt the user to run
/wdp-prd-accept <id>.
Non-git fallback: when no git repository is detected, clearly warn that worktree isolation is unavailable, ask whether to still dispatch serially or abandon; never continue silently.
/wdp-prd-accept — Accept
- The card status==needs-review, otherwise prompt to dispatch first.
- Merge the subagent's worktree branch into the current working branch.
- Run the full integration test suite; on failure → leave the card as needs-review, record the failure reason, and prompt to fix or roll back.
- Run a code review (reuse
superpowers:requesting-code-review). - Present the change summary + review verdict to the user → user confirms.
- On confirmation → status→accepted→done, fill in the acceptance record, rewrite
execution-plan.md. - After acceptance, remove the merged worktree (reuse the cleanup flow of
superpowers:using-git-worktrees).
/wdp-prd-new — Discuss and create a requirement
- Confirm this project's
.wdp-prdpointer exists (if missing, go through Initialization first). - Invoke
superpowers:brainstormingto discuss the requirement with the user, producing a design document (saved to the project'sdocs/superpowers/specs/). - Create a new card
backlog/R-###.mdperreferences/card-template.md:- id auto-incremented (current max + 1); status=draft; priority set by the user or default medium.
- created/updated = today.
- Write the design-document path into the
Design Docsection.
- Rewrite
execution-plan.md.
Requirement Cards
See references/card-template.md for the format. Copy the template when creating.
Error Handling
| Situation | Handling |
|---|---|
| Non-git repository | Worktree isolation unavailable → warn clearly, fall back to serial/non-isolated (see dispatch flow) |
| Subagent failure | Card → blocked, report the reason, update execution-plan |
| Dependency cycle | Detect and report the cycle, do not dispatch |
| Missing dependency | Report the dependency id does not exist, prompt to check depends_on |
| Same-batch conflict | Force picking only one |
| Review failed | Card stays needs-review, record the verdict |
| User did not confirm | Card stays needs-review |
| No Agent tool | Fall back to a manual guided flow |
.wdp-prd missing | Trigger initialization |
Verification
Dry-run all scenarios (S1–S6) per references/test-scenarios.md. The skill passes only when every Expected is met.
Related skills
- Downloads
- 496All time
- Security audit
- Review
- Last updated
- 3mo ago
- Current version
- v1.0.0
- License
- MIT-0
