pm-requirements-v1

# 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) ```bash 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; authentica...