update-prd

Update the Product Requirements Document: $ARGUMENTS

Core references. A citation of the form workflows-core:<name> names a shared reference in the workflows-core plugin. Load it with Skill(skill: "workflows-core:reference", args: "<name>") — never by path: ${CLAUDE_PLUGIN_ROOT} resolves to this plugin, which does not carry it.

/update-prd refreshes an existing Product Requirements Document (PM phase). It covers routine refreshes (new information, scope tweaks, wording) and the rare obstacle-driven re-do (a human read an ARD/spec finding, discussed it, and decided the PRD must change). The PRD is product-level — what / why / for-whom, not how. Zero code scan; no repos.

Usage: /update-prd <KEY> [@transcript-or-notes ...] [--no-docs] [--docs <path>] (--no-docs turns off documentation grounding for the run — see Phase 1). --docs <path> — points documentation grounding at that root for this run instead of ${DOCS_PATH:-/workspace/docs}; strip the flag and its value together before any remaining-argument classification, or the path is read as part of the address. Declared for every consumer by workflows-core:docs-grounding §1's Flags first rung, which resolves it; this command only has to recognise it and pass the invocation through.

Phase 0 — Resolve inputs

1. Flags. Strip --no-docs (boolean) and --docs <path> — the flag and its value together — from $ARGUMENTS before anything else reads it. Both are carried to Phase 1's resolve-docs-grounding call and change nothing else. This step is load-bearing rather than tidy: Phase 1 step 5 consumes "any @transcript / notes path(s) passed in $ARGUMENTS", so an unstripped --docs value is read in as a grounding source and its content reaches the PRD.
2. KEY (mandatory). Parse the first token that is neither a flag nor a flag's value — --docs each consume the token after them (step 0), and a value skipped as "non-flag" would be read as the key and validate it with key-valid (workflows-core:addressing §1) — the grammar is that file's, cited rather than copied here. If absent or malformed, stop: UPDATE_PRD_NEEDS_KEY: /update-prd needs the PRD's key — '/product-workflows:update-prd <KEY>'. The grammar is a superset of the two-segment form — every key that validated before still validates, so a PRODUCT-1234 refresh behaves exactly as it did — and it is the one this command needs for the same reason step 3's folder resolution is: a PRD authored inside a BRD slice by /create-prd on the BRD route carries a three-segment key (EPIC-008-01), and /create-prd redirects here on finding it. A validation narrower than /create-prd's would refuse that redirect at the door, which is the identical dead-end step 3 exists to close, one step earlier.
3. $SPECS_PATH (required). If unset, stop naming SPECS_PATH (choices: ["Set SPECS_PATH (enter the path)", "Cancel"]).
4. Feature folder. Resolve it with resolve-address <KEY> (Skill(skill: "workflows-core:reference", args: "addressing resolve-address"), §3), which searches every level §3 bounds and carries §5's legacy fallback; ambiguous → stop, naming every match and @<path> as the way through. status: absent is a stop, not a folder to create: surface the key dir not found rule in Skill(skill: "workflows-core:reference", args: "escalation-rules") (choices: ["Re-enter key", "Cancel"]) and name /product-workflows:create-prd <ADDRESS> as the run that authors a PRD where none exists. Named unqualified here and only conditionally at step 4, and the difference is what resolved: nothing did. There is no folder, so there is no brd-link.md, no gate set and no kind to test — ${CLAUDE_PLUGIN_ROOT}/references/coverage-ledger-format.md §5.2's Only a BRD-route folder has a gate set at all is the case that applies, and the container refusal that is /create-prd's third has no folder to fire on. Step 4 reports a folder that does exist, which is why it tests all three before it names that command. No matching rule is written here — §5 owns it.
5. Resolve the base PRD. It is the prd.md in the folder step 3 resolved — the only copy there is, and therefore authoritative without a test. Absent → stop gracefully:

   UPDATE_PRD_NO_PRD: <ADDRESS> resolves a folder at <path> holding no prd.md, and /update-prd refreshes an existing PRD rather than authoring one. <the remedy, per the row below that matches>