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.

Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.

Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.

Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.

Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill writes the durable lessons entry that outlives it.

Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.

Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.

2 hooks across 2 events