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

Document edge cases and error states for a feature

Design an A/B test or experiment

Document experiment results and learnings

Define a testable hypothesis with success metrics

Specify event tracking and analytics instrumentation

Synthesize user research interviews into insights

Create a Jobs to be Done canvas

Run the Feature Kickoff workflow (problem → hypothesis → PRD → stories)

Create a comprehensive pre-launch checklist

Create a structured lessons learned entry

Create an opportunity solution tree

Generate a product or marketing persona using the v2.5 canonical template contract

Document a pivot or persevere decision

Create a new PM skill for the pm-skills library with gap analysis, classification, and a complete Skill Implementation Packet

Apply targeted improvements to an existing PM skill based on feedback, validation reports, or convention changes

Audit an existing PM skill against structural conventions and quality criteria, producing a validation report with actionable recommendations

Create a Product Requirements Document

Create a clear problem statement with success criteria

Document backlog refinement session outcomes

Create user-facing release notes

Facilitate and document a team retrospective

Create a one-page solution overview

Document the results of a technical or design spike

Document stakeholder needs and influence

Generate user stories with acceptance criteria

Purpose: cross-LLM decision log for pm-skills. Per-agent details remain in `AGENTS/<agent>/DECISIONS.md`; this file holds the canonical summary and pointers.

**Status:** v2.8.0 released and tagged — PM skill lifecycle complete (Create → Validate → Iterate)

**Status:** Accepted

- Active; last updated: 2026-03-22

**Status:** Accepted

This folder is the Codex working area for `pm-skills`.

Worktrees let you have multiple checked-out branches from the same repo at the same time in different folders.

Use this at the end of every implementation session to produce a decision-complete handoff artifact with clear restart instructions.

Author: Claude Opus 4.6

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.

Documents edge cases, error states, boundary conditions, and recovery paths for a feature. Use during specification to ensure comprehensive coverage, or during QA planning to identify test scenarios.

Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features, products, or major updates to ensure nothing is missed.

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.

Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.

Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.

Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.

Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.

Creates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.

Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings.

Documents stakeholder needs, concerns, and influence for a project or initiative. Use when starting projects, managing complex stakeholder relationships, or ensuring alignment across organizational boundaries.

Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract. Use when shaping artifact perspective, stress-testing decisions, or framing product and GTM strategy.

Creates a structured lessons learned entry for organizational memory. Use after projects, incidents, or significant learnings to capture knowledge for future teams and initiatives.

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.

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.

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.

Designs an A/B test or experiment with clear hypothesis, variants, success metrics, sample size, and duration. Use when planning experiments to validate product changes or test hypotheses.

Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.

Specifies event tracking and analytics instrumentation requirements for a feature. Use when defining what data to collect, ensuring consistent tracking implementation, or documenting analytics requirements for engineering.

Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->