Alternatives
pm-requirements-v1 alternatives for AI agents.
Compare similar skills by workflow fit, trust score, quality, GitHub adoption, maintenance, and install readiness.
Current skill
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).