pm-execution

Create a comprehensive Product Requirements Document from a feature idea, problem statement, or brain dump — iterative, sized to your initiative, publishable to Confluence

Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts

Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results

Convert a PRD into Jira-ready Epics and Stories — reads from text, file, or Confluence; optional Figma URL for design context. Uses Job Story format with strategic WHY. Epic + Story level only, no tasks.

Run a pre-mortem risk analysis on a PRD, launch plan, or feature — identify what could go wrong before it does

Run a complete quarterly planning session — OKRs, roadmap, risks, and decisions — calibrated to your level

Expert CPO-level PRD review — scores across 8 dimensions, flags assumptions and biases, runs adversarial perspectives, and coaches the PM on how to improve

Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes

Map stakeholders on a Power × Interest grid and create a tailored communication plan

Draft a structured stakeholder update calibrated to your seniority and audience — team, leadership, or board level

Generate a sign-off-ready test plan from PRD, Figma, and Jira. PM-first — validates the feature ships in the right state, the user experience holds under failure, and the business is protected. Produces manual test cases with a PM sign-off gate.

Convert a feature-based roadmap into an outcome-focused roadmap that communicates strategic intent

Break a feature or PRD into sprint-ready backlog items using the hybrid Job Story + WWA format with INVEST validation and acceptance criteria

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.

Draft a structured stakeholder update — weekly, monthly, or milestone-based — calibrated to the user's seniority and audience. Use when someone asks to write a stakeholder update, status update, leadership update, weekly update, exec update, board update, or 'update for my CEO/manager/team'. Detects whether the user is an IC/PM writing to their manager, a VP/CPO writing to CEO or leadership team, or anyone writing a board-level update. Always asks for level and update type if not stated. Different from stakeholder-map (which maps the landscape). This skill produces the actual communication artifact. Commands: /stakeholder-update, /write-update, /exec-update

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Convert a PRD into Jira-ready Epics and Stories using Job Story format (When/I want/So I can) with WWA strategic context. Reads PRD from text, file, or Confluence. Accepts Figma URL for design context. Outputs Epic + Story hierarchy only — no tasks. Use when breaking down a PRD into a sprint-ready backlog.

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

Run an adaptive quarterly planning session that calibrates to the user's level. Use when someone asks to do quarterly planning, Q-planning, build a QBR, set quarterly goals, align on roadmap for the quarter, run a planning cycle, or prepare a board-ready quarterly review. Detects whether the user is an IC/team PM (team-level OKRs + roadmap alignment), a VP/CPO (P&L + strategic resourcing + cross-functional alignment), or preparing a QBR for CEO/board (financial narrative + strategic priorities + decisions needed). Always ask for level first if not provided. Commands: /quarterly-planning, /plan-quarter, /qbr

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Expert CPO-level PRD review. Classifies the PRD domain, generates expected coverage for that domain, hunts unstated assumptions and biases, scores across 8 dimensions out of 100, and coaches the PM on how to grow. Use when reviewing an existing PRD for quality, completeness, or readiness.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.

Generate a sign-off-ready test plan from PRD, Figma designs, and Jira epics. PM-first perspective: validates the feature ships in the right state, the user experience holds under failure, and the business is protected. Covers happy path, validation, error recovery, integration failures, financial accuracy, state transitions, and access control. Outputs prioritised manual test cases with a PM sign-off gate.