claude

pm-execution

Execution and product management skills: PRDs, solution briefs, ADRs, edge case analysis, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, general-purpose writing, meeting preparation, and stakeholder updates.

9 on GitHubby Tarun Narangv1.2.0MITupdated 1 month agoproduct-management
/

Plugin pm-execution from marketplace pm-skills in tarunccet/pm-skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (20)

  • adr

    Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any de

  • brainstorm-okrs

    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-prd

    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.

  • edge-cases

    Systematically identify error states, boundary conditions, and recovery paths for a feature using the BOUNDARY method — reduces post-launch defects by surfacing what specs miss. Use after writing a PRD, before sprint planning, during QA planning, or when reviewing acceptance criteria for completenes

  • job-stories

    Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

  • meeting-prep

    Prepare for any PM meeting — 1:1s, stakeholder alignments, leadership reviews, and cross-functional planning sessions with structured talking points, anticipated questions, and success criteria. Use when preparing for a meeting, building an agenda, or anticipating stakeholder questions.

  • outcome-roadmap

    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.

  • pre-mortem

    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 identi

  • prioritization

    Unified prioritization skill that adapts to what you're prioritizing: features (ICE/RICE/Opportunity Score), assumptions (Impact × Risk matrix + experiment design), backlog items (strategic alignment + effort), or general trade-offs. Includes reference to all 9 prioritization frameworks. Use when pr

  • release-notes

    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.

  • retro

    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.

  • solution-brief

    Create a lightweight one-page solution pitch that summarizes the problem, proposed approach, alternatives considered, risks, success metrics, and effort estimate with a clear next-step recommendation (PRD / spike / kill / pivot). Serves as the decision gate between discovery and full requirements. U

  • sprint-plan

    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.

  • stakeholder-map

    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.

  • stakeholder-update

    Create structured stakeholder updates, status reports, and executive summaries — weekly updates, quarterly reviews, and quick status messages with audience-calibrated detail. Use when writing a status update, preparing a progress report, creating an executive summary, or sharing project status.

  • summarize-meeting

    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.

  • test-scenarios

    Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.

  • user-stories

    Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

  • writer

    General-purpose PM writing assistant for briefs, emails, status updates, Slack messages, proposals, and presentations — adapts tone and structure to audience. Use when drafting any PM communication, writing an email, preparing a brief, or polishing a message.

  • wwas

    Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.

Slash commands (11)

  • /pm-execution:meeting-notes

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

  • /pm-execution:plan-okrs

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

  • /pm-execution:pre-mortem

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

  • /pm-execution:prep-meeting

    Prepare for any PM meeting with structured talking points, anticipated questions, and success criteria

  • /pm-execution:sprint

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

  • /pm-execution:stakeholder-map

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

  • /pm-execution:test-scenarios

    Generate comprehensive test scenarios from user stories or feature specs — happy paths, edge cases, and error handling

  • /pm-execution:transform-roadmap

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

  • /pm-execution:write-prd

    Create a comprehensive Product Requirements Document from a feature idea or problem statement

  • /pm-execution:write-stories

    Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria

  • /pm-execution:write-update

    Create a polished stakeholder update or status report tailored to your audience — executives, managers, or team

View source on GitHub

More from tarunccet/pm-skills

All 9 plugins →

Interactive Socratic learning modules for PMs: guided exercises, simulations, and quiz checkpoints for discovery, strategy, metrics, prioritization, user research, stakeholder management, AI product management, and vibe coding.

12 skills · 14 commands

9

Product strategy skills for PMs: vision, strategy canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, monetization, pivot decisions, and devil's advocate stress-testing.

14 skills · 6 commands

9

Product discovery skills for PMs: problem statements, testable hypotheses, ideation, experiments, assumption testing, lean validation, and customer interview synthesis.

12 skills · 6 commands

9

AI product management skills: model evaluation, responsible AI, AI metrics, prompt engineering, AI feature specs, build-vs-buy decisions, AI user research, data strategy, incident response, and competitive analysis.

8 skills · 6 commands

9

Data analytics skills for PMs: SQL query generation, cohort analysis, A/B test analysis, funnel analysis, event tracking planning, metric definition, and North Star metric definition.

7 skills · 7 commands

9

Vibe coding skills for PM-builders: write AI coding specs, plan prototypes, make technical architecture decisions, review AI-generated code, run deployment checklists, debug with AI assistance, and understand codebases in PM-friendly terms.

7 skills · 6 commands

9

Similar plugins

Statically analyze a local JS/Electron app you're authorized to study, with file+line evidence, and build an original reimplementation of what you find. Experimental. Phase 1: JS/Electron static analysis. Phase 2: native ELF/PE/Mach-O container inspection. Phase 3: .NET assembly metadata. Phase 4: EVM bytecode inventory. Phase 5: CUDA fatbin, cubin and PTX inventory. Parses, never executes. Dynamic analysis is a future phase, not yet implemented.

1 skill · 1 command · 1 agent

ruvnet/ruflo 81,589

gitnexus

claudecodex

Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.

12 skills · 1 MCP server · hooks

abhigyanpatwari/GitNexus 48,482

Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.

13 skills · 9 commands · 1 MCP server

anthropics/claude-plugins-official 47,076

Bring Pendo product analytics into Claude: account health, feature adoption, session replay lookup and triage, feedback analysis, and data-informed planning grounded in real usage data. Requires the Pendo connector and a Pendo subscription.

6 skills · 2 MCP servers

anthropics/knowledge-work-plugins 35,601

context-mode

claudecodex

Context window saver for 10 coding agents. Local and free: sandboxed code execution, FTS5 search, session continuity.

3 skills · 1 MCP server

mksglu/context-mode 34,004

33 C-level advisory skills (install the separate companion c-level-agents plugin for the persona layer): virtual board of directors (CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO) plus General Counsel, CDO, CAIO, CCO, and VP of Engineering (DORA delivery throughput analyzer, engineering hiring funnel calculator with conversion + pipeline gap, eng team structure designer with squad/tribe + manager-trigger), executive mentor, founder coach, orchestration (Chief of Staff, board meetings, decision logger), strategic capabilities (board deck builder, scenario war room, competitive intel, M&A playbook), culture frameworks. The 13 cs-* persona agents + 21 /c-level-agents:* slash commands (founder-mode router, office-hours intake, multi-role boardroom, strategic sprint pipeline, cross-model consensus, cooldown freeze) ship in the companion c-level-agents plugin.

34 skills · hooks

alirezarezvani/claude-skills 29,725

Maintain pm-execution?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins9 plugins