pm-skills

Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem)

Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)

Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories)

Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)

Drafts CHANGELOG entries from git log applying pm-skills CHANGELOG hygiene rules from CLAUDE.md: describe what changed (not where), public paths only, never reference gitignored _NOTES/ or _agent-context/SESSION-LOG/ or docs/internal/efforts/. Distinguishes user-facing from internal-only commits. Returns a draft for maintainer review and edit. Explicit invocation only. Used standalone via the utility-pm-changelog-curator dispatch skill (or @-mention) or chained from pm-release-conductor at gate G2.

Use proactively after any PM-artifact-producing skill completes (deliver-prd, foundation-meeting-recap, foundation-okr-writer, foundation-persona, foundation-lean-canvas, discover-interview-synthesis, define-problem-statement, define-hypothesis, deliver-edge-cases, deliver-user-stories, deliver-acceptance-criteria, iterate-retrospective, iterate-lessons-log, and other Triple Diamond phase skills). Runs adversarial review. Finds weaknesses, not wins. Returns findings graded P0/P1/P2/P3 with concrete fix suggestions for each. Reads canonical standards docs at invocation time.

Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance past a failed gate. No bypass possible (--skip-gates removed per D24). Tags only the SHA captured at G2.5 (prevents broken-tag class per D22). G4 P0 sub-checks block "Release complete" output (per D23). Maintainer-facing; explicit invocation only.

Repo-level cross-cutting governance auditor. Runs the full enforcing validator suite (frontmatter lint, command paths, AGENTS.md sync, family contracts, link validity, count consistency, workflow generator coverage, etc.) via scripts/pre-tag-validate.{sh,ps1}, aggregates results, and surfaces cross-cutting issues no single validator catches alone (sample gaps, aggregate counter drift, family contract orphans / phantoms, thread imbalance, deprecated references, etc.). Re-derives aggregate counters across CONTEXT.md + AGENTS.md + README.md. Returns layered output (full report + Status Summary + Status YAML) graded P0/P1/P2/P3. Explicit invocation only - never proactive. Used by maintainers pre-release and by users running repo-health checks.

Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.

Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.

2 hooks across 2 events