Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied.
Documents stakeholder needs, concerns, and influence for a project or initiative. Use when starting projects, managing complex stakeholder relationships, or ensuring alignment…
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…
Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes.
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character…
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences.
Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference.
Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key…
Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract.
Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness.
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…
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…
Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before…
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting.
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…
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language.
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions.
Generates user stories with clear acceptance criteria from product requirements or feature descriptions.
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.
Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to…
Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end).
Creates a structured lessons learned entry for organizational memory. Use after projects, incidents, or significant learnings to capture knowledge for future teams and initiatives.
Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety),…
Designs an A/B test or experiment with clear hypothesis, variants, success metrics, sample size, and duration.
Creates a structured competitive analysis comparing features, positioning, and strategy across competitors.
Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made.
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.
Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources.
Specifies event tracking and analytics instrumentation requirements for a feature. Use when defining what data to collect, ensuring consistent tracking implementation, or…
Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions.
Produces a one-page lean canvas across nine interlocking blocks (problem, customer, UVP, solution, channels, revenue, cost, metrics, unfair advantage) with optional inline HTML…
Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent.
Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip…
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items.
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations.
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…