| name | new |
| description | Add one new Work Package to an already-planned project — short interview, writes the skeleton PRD and refreshes the dependency map. Use /prd:setup instead if the project has no PRDs yet. |
| argument-hint | [optional: name or area of the new WP] |
/prd:new — add a Work Package
Adds one new WP to a project already planned with prd-kit. The result is a
skeleton PRD correctly wired into the dependency map — specifying it in depth stays
in /prd:fill.
Step 1 — Load context
- Locate the PRD folder (
docs/prds/, docs/PRD/ or prds/ — whichever holds
WP-*.md files). If none exists, stop and suggest /prd:setup.
- Read the frontmatter of every existing
WP-*.md: ids in use, statuses, dependencies,
owners, milestones. Pick the next free WP-NN.
- If
$ARGUMENTS names the WP or its area, start from that; otherwise ask in one
sentence what the WP is.
Step 2 — Mini-interview (one round, max ~4 questions)
Skip anything you can infer from the repo or the existing PRDs:
- Objective: desired end state and why it matters (product level).
- Scope: what's in, what's out — each excluded item names its destination WP.
- Dependencies: which existing WPs must be done first? Challenge unnecessary ones —
every dependency delays this WP.
- Metadata: size (S/M/L), owner, milestone, external blocker if any.
If the WP feels XL or its scope overlaps an existing WP, say so and propose a re-slice
before writing anything.
Step 3 — Write the skeleton
- Copy the structure of
${CLAUDE_PLUGIN_ROOT}/templates/PRD-SKELETON.md to
WP-NN-<slug>.md in the PRD folder.
- Fill the frontmatter (
status: skeleton), §1 Objective, §2 Scope and §3 Open
questions (capture now everything /prd:fill will need to resolve).
Step 4 — Rewire and refresh
- If the new WP should be a dependency of existing WPs, update their
depends_on (with
the user's confirmation) — a new foundation piece usually slots under others.
- Run the
/prd:map procedure to regenerate ROADMAP.md and map.html.
- If the project mirrors WPs to a tracker (Linear or other), offer to create the issue —
see
${CLAUDE_PLUGIN_ROOT}/docs/LINEAR.md. Only with explicit confirmation.
Do not commit unless asked.
