pm-requirements-v1
The requirements cycle, turn a strategy statement, a release target and a set of affected surfaces into an evidence-tagged, gated HANDOFF PACKAGE: spec.md, plan.md, data-model.md, contracts/, slices.json, a design gate and a case contract, plus the record that makes all of it auditable. Five phases: P0 context lock (the north-star metric elicited fresh every cycle) → P1 research → P2 strategy → P3 product spec → P4 handoff. Use when someone says "run the requirements cycle", "write the PRD / handoff package for <feature>", "prep the design gate", "requirements for the next release", or hands a strategy statement that needs to become buildable work. NOT for writing code, running CI, deploying or merging, an engineering toolchain owns those; NOT for release verification (pm-verify-release-v1); NOT for scoring a backlog batch (pm-portfolio-v1).
naderelewa · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add naderelewa/Product-to-Prod --skill pm-requirements-v1About this skill
name: pm-requirements-v1 description: | The requirements cycle, turn a strategy statement, a release target and a set of affected surfaces into an evidence-tagged, gated HANDOFF PACKAGE: spec.md, plan.md, data-model.md, contracts/, slices.json, a design gate and a case contract, plus the record that makes all of it auditable. Five phases: P0 context lock (the north-star metric elicited fresh every cycle) → P1 research → P2 strategy → P3 product spec → P4 handoff. Use when someone says "run the requirements cycle", "write the PRD / handoff package for ", "prep the design gate", "requirements for the next release", or hands a strategy statement that needs to become buildable work. NOT for writing code, running CI, deploying or merging, an engineering toolchain owns those; NOT for release verification (pm-verify-release-v1); NOT for scoring a backlog batch (pm-portfolio-v1). argument-hint: " --release --surfaces <a,b,c> [--pack ] [--stack ]" user-invocable: true
pm-requirements-v1, strategy statement → handoff package
Build a rigorous, evidence-tagged requirements case for ONE release scope and close it as a handoff package: a directory a sceptical reviewer can verify in minutes and an engineering toolchain can consume without a single paste.
This verb is the product-and-strategy half of the loop. It produces documents and the design-gate scaffold. It writes no code, runs no tests, merges nothing, and authors no engineering records.
The boundary is hard. Downstream of the final gate, everything belongs to whoever builds it.
Where an engineering toolchain is configured, its surface registry is READ-ONLY ground truth, read
surface names from it, never edit it, never hardcode its values. Where none is configured this verb
runs in standalone mode and says so; see references/eng-handoff-adapter.md at the plugin root.
Preflight (run first)
PKG_ROOT="${CLAUDE_PLUGIN_ROOT:-${PKG_ROOT:-}}"
[ -n "$PKG_ROOT" ] && [ -r "$PKG_ROOT/.claude-plugin/plugin.json" ] || { echo "STOP: set PKG_ROOT to this package's root directory, the one holding .claude-plugin/plugin.json, then re-run."; exit 2; }
bash "$PKG_ROOT/scripts/preflight.sh" pm-requirements-v1 [--stack <keys>]
A job-scoped capability check against config/dependencies.json. Run it BEFORE P0 with no --stack.
A miss on a required capability blocks the run, and every miss prints its exact one-time fix
(--setup performs the installable ones; authentication flows print instructions and are never
auto-run). Conditional capabilities are resolved at right-sizing: once the stack is locked, re-run
with the matching keys. A selected-conditional miss blocks exactly like a required one. A missing
capability notifies and blocks, it never silently degrades into a quieter, wronger answer.
What a run delivers, standalone vs supercharged (projected from config/dependencies.json;
the miss discipline above is unchanged):
- STANDALONE (required only,
python3, andshasumorsha256sum): the full P0→P4 cycle over run-supplied and pack evidence: locked constants, a tagged evidence ledger, the classified spec, the assembled handoff package. Claims that would need live analytics or a docs workspace ride NEEDS-CONFIRMATION rows instead of being measured. This is a complete deliverable, not a stub. - SUPERCHARGED, each locked
--stackkey adds its capability rows, one or more:eng-handoff(the downstream registry + contract check) ·analytics-verification(measured funnel and behaviour claims instead of NEEDS-CONFIRMATION rows) ·design-extraction(design-kit parity reads) ·backlog-sync(issue-tracker cross-checks) ·workspace-docs(workspace pages as citable sources) ·repo-state(repository and change-request state reads).
What you elicit, echo, and lock
Elicited at cycle open, echoed back, then frozen as P0 constants:
| Constant | Notes |
|---|---|
{company} {product} | who and what the cycle is for. Resolved from the selected pack, or elicited. Never assumed. |
{strategy statement} | the strategic intent this cycle serves, one paragraph, with its source cited |
{release target} | which release or train these requirements are for |
{surfaces} | the affected surfaces. From the downstream registry when configured; otherwise from the answer, marked unverified |
{period} {geography} | cycle window and market scope |
{nsm} + {leading metric} | elicited fresh EVERY cycle, never defaulted from a prior one |
{owner} | the named person who accepts this work, written down before the run starts |
{decision shape} | who holds decision RIGHTS: solo (one person decides) · domains (named domain owners) · squads (layered approval). Identified by rights, never by headcount |
When a prior cycle exists, open with the delta question, "last cycle the north-star metric was X and the scope was Y; still true?", and confirm the delta instead of re-eliciting from zero. Supplied context counts as an answer. Stop and ask only at real boundaries: a weak or stale source, two genuinely valid framings, an invalidated metric assumption, an irreversible or external action. Never stop to ask for context you could go and read.
The phase spine
P0 context lock ─→ right-sizing lock ─→ P1 research ─→ P2 strategy ─→ ■ GATE 1
─→ P3 product spec ─→ P4 handoff package ─→ ■ GATE 2 ─→ finalisation ─→ ■ GATE 3 (seal + ship)
Each phase produces exactly ONE canonical output file. If context feels lost, re-ground from those files rather than from the conversation.
Where those files land. Write every phase output under the folder this run selected; with none selected, the session's already-authorized working path; with no authorized writable path at all, STOP and ask for one before any artifact is written. The harness enforces that boundary either way, the ask is what
Read the complete source ↗