Execution-Related Skills and Commands in the PM Skills Marketplace: Complete Inventory

The PM Skills Marketplace organizes product management capabilities into domain-specific modules, with the execution domain providing 16 markdown-based skills and 11 CLI-style commands for generating deliverables like user stories, PRDs, and sprint plans.

The phuryn/pm-skills repository implements a structured marketplace for product management capabilities. Within this system, execution-related skills and commands form the operational backbone, transforming abstract product strategy into concrete deliverables through standardized markdown schemas and chat-oriented interfaces.

What Are Execution Skills in the PM Skills Marketplace?

The execution domain in phuryn/pm-skills contains skills—declarative markdown files that encode step-by-step processes for creating specific artifacts. Each skill resides in its own subdirectory under pm-execution/skills/ and follows a strict YAML frontmatter schema:

---
name: Skill Name
description: Concise explanation of the deliverable
---

These files define templates, acceptance criteria, and reasoning frameworks that ensure consistent output quality across different product management contexts.

Complete Inventory of Execution Skills

The repository maintains 16 distinct execution skills, each serving a specific phase of the product development lifecycle.

Backlog and Story Definition

• wwas: Generates backlog items using the Why-What-Acceptance format. Source: pm-execution/skills/wwas/SKILL.md
• user-stories: Creates user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Source: pm-execution/skills/user-stories/SKILL.md
• job-stories: Produces Jobs-to-be-Done style narratives using the "When... I want... so I can..." structure. Source: pm-execution/skills/job-stories/SKILL.md

Planning and Strategy

• sprint-plan: Calculates team capacity, selects backlog items, maps dependencies, and identifies risks for iterative development. Source: pm-execution/skills/sprint-plan/SKILL.md
• outcome-roadmap: Visualizes product trajectories focused on measurable outcomes rather than output features. Source: pm-execution/skills/outcome-roadmap/SKILL.md
• prioritization-frameworks: Applies systematic ranking methods including MoSCoW, RICE, and Kano models. Source: pm-execution/skills/prioritization-frameworks/SKILL.md
• brainstorm-okrs: Facilitates objective and key results drafting for initiative alignment. Source: pm-execution/skills/brainstorm-okrs/SKILL.md

Documentation and Analysis

• create-prd: Constructs comprehensive Product Requirements Documents using an 8-section template covering market analysis, objectives, and value propositions. Source: pm-execution/skills/create-prd/SKILL.md
• strategy-red-team: Conducts adversarial review of PRDs to surface hidden assumptions and failure points. Source: pm-execution/skills/strategy-red-team/SKILL.md
• pre-mortem: Anticipates launch failures and mitigation strategies before commitment. Source: pm-execution/skills/pre-mortem/SKILL.md
• stakeholder-map: Builds visual influence diagrams mapping roles, power dynamics, and communication pathways. Source: pm-execution/skills/stakeholder-map/SKILL.md

Quality Assurance and Operations

• test-scenarios: Derives detailed QA test cases from user story inputs. Source: pm-execution/skills/test-scenarios/SKILL.md
• dummy-dataset: Generates synthetic data for development and testing environments. Source: pm-execution/skills/dummy-dataset/SKILL.md
• release-notes: Compiles shipped feature documentation for customer communication. Source: pm-execution/skills/release-notes/SKILL.md
• summarize-meeting: Distills raw meeting notes into concise action items and decisions. Source: pm-execution/skills/summarize-meeting/SKILL.md
• retro: Guides sprint retrospectives with structured prompts and action-item capture. Source: pm-execution/skills/retro/SKILL.md

Execution Commands and Invocation Syntax

Commands in the PM Skills Marketplace serve as typed interfaces that instantiate skills with specific parameters. Located in pm-execution/commands/, these markdown files define the parsing logic, argument validation, and output formatting that bridge user input and skill execution.

Each command supports slash-style invocation typical of chat-oriented interfaces like Slack bots.

Story and Backlog Commands

• /write-stories: Invokes user-stories, job-stories, or wwas skills based on the first argument. Syntax: /write-stories [user|job|wwa] <feature description>. Source: pm-execution/commands/write-stories.md
• /test-scenarios: Generates QA scenarios from a provided user story. Syntax: /test-scenarios <user-story>. Source: pm-execution/commands/test-scenarios.md

Planning and Strategy Commands

• /sprint: Executes the sprint-plan skill with team capacity and backlog inputs. Syntax: /sprint <team info> <backlog>. Source: pm-execution/commands/sprint.md
• /plan-okrs: Initiates the brainstorm-okrs skill for objective setting. Syntax: /plan-okrs <objective>. Source: pm-execution/commands/plan-okrs.md
• /transform-roadmap: Converts existing roadmap formats into outcome-driven structures. Syntax: /transform-roadmap <roadmap source>. Source: pm-execution/commands/transform-roadmap.md
• /stakeholder-map: Generates influence maps for project contexts. Syntax: /stakeholder-map <project>. Source: pm-execution/commands/stakeholder-map.md

Documentation and Review Commands

• /write-prd: Triggers the create-prd skill to generate full requirements documents. Syntax: /write-prd <product name> <feature description>. Source: pm-execution/commands/write-prd.md
• /red-team-prd: Executes adversarial review via the strategy-red-team skill. Syntax: /red-team-prd <prd>. Source: pm-execution/commands/red-team-prd.md
• /pre-mortem: Runs failure anticipation analysis. Syntax: /pre-mortem <initiative>. Source: pm-execution/commands/pre-mortem.md
• /meeting-notes: Processes raw notes into structured summaries. Syntax: /meeting-notes <raw notes>. Source: pm-execution/commands/meeting-notes.md
• /generate-data: Creates synthetic datasets for testing. Syntax: /generate-data <schema>. Source: pm-execution/commands/generate-data.md

Practical Implementation Examples

The following snippets demonstrate how automation scripts or chatbots invoke these execution commands against the PM Skills Marketplace engine.

Generating User Stories with Format Selection

/write-stories user Allow users to export reports as PDF and CSV

This invocation routes to the user-stories skill in pm-execution/skills/user-stories/SKILL.md, returning structured stories with titles, descriptions, and acceptance criteria formatted according to the 3 C's framework.

Building a Sprint Plan with Parameters

/sprint team:5 velocity:30 backlog:backlog.md

The sprint-plan skill parses the team size and velocity constraints, selects appropriate stories from the referenced backlog file, maps interdependencies, and outputs a markdown sprint plan ready for team review.

Creating a Product Requirements Document

/write-prd MyApp "Add a dark-mode toggle to the settings page"

This triggers the 8-section PRD template from pm-execution/skills/create-prd/SKILL.md, pre-populating sections for market analysis, objectives, value proposition, and functional requirements.

Summary

The execution domain in phuryn/pm-skills provides a comprehensive toolkit for product management operations:

• 16 specialized skills covering backlog creation, planning, documentation, and quality assurance
• 11 CLI-style commands that expose skills through chat-oriented interfaces with structured argument parsing
• Standardized markdown schemas ensuring consistent artifact generation across all execution workflows
• Direct source file mapping with skills residing in pm-execution/skills/ and commands in pm-execution/commands/

Frequently Asked Questions

What is the difference between a skill and a command in the PM Skills Marketplace?

A skill is a declarative markdown file containing process logic, templates, and acceptance criteria for creating a specific artifact. A command is an executable interface that parses user input, handles missing parameters through prompting, and routes requests to the appropriate skill. Skills define how to create something; commands define how users invoke that creation.

How do I invoke execution skills without using the predefined commands?

While the repository provides standardized commands in pm-execution/commands/, you can directly reference any skill file by parsing its YAML frontmatter and markdown content. Each skill follows the schema defined in pm-execution/README.md, allowing custom implementations to instantiate the templates directly without the command wrapper's argument parsing logic.

Which execution skill should I use for sprint retrospectives?

Use the retro skill located at pm-execution/skills/retro/SKILL.md. This skill provides structured prompts for gathering feedback, identifying process improvements, and capturing action items. While there is no dedicated /retro command in the current inventory, the skill can be invoked directly or wrapped in a custom command using the same patterns found in pm-execution/commands/meeting-notes.md.

Can I customize the PRD template generated by the create-prd skill?

Yes. The create-prd skill in pm-execution/skills/create-prd/SKILL.md uses an 8-section markdown template. You can modify the source file directly to adjust sections, add organizational-specific headers, or change the prompt logic. The /write-prd command will automatically use the updated template the next time it invokes the skill.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}