pm-skills

Generate acceptance criteria with Given/When/Then

Create an Architecture Decision Record

Create a structured competitive analysis

Specify requirements for an analytics dashboard

Document the reasoning behind design decisions

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 /pm-draft-changelog 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 (skill-without-command, sample gaps, aggregate counter drift, family contract orphans / phantoms, thread imbalance, sub-agent without companion command, 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.

Defines a testable hypothesis with clear success metrics and validation approach. Use when forming assumptions to test, designing experiments, or aligning team on what success looks like.

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.

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.