mirror of
https://github.com/phuryn/pm-skills.git
synced 2026-06-13 23:14:56 +03:00
Improve skill discoverability
This commit is contained in:
Pawel Huryn
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "pm-execution",
|
||||
"version": "1.0.0",
|
||||
"version": "1.0.1",
|
||||
"description": "Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.",
|
||||
"author": {
|
||||
"name": "Paweł Huryn",
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: brainstorm-okrs
|
||||
description: "Brainstorm team-level OKRs aligned with company objectives. Creates 3 OKR sets with qualitative objectives and quantitative key results. Use when setting quarterly OKRs, aligning team goals with company strategy, or drafting objectives. Triggers: OKRs, objectives key results, team goals, quarterly planning, goal setting."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
# Brainstorm Team OKRs
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: create-prd
|
||||
description: "Create a Product Requirements Document using a comprehensive 8-section template covering summary, background, objectives, market segments, value propositions, solution details, and release planning. Use when writing a PRD, documenting product requirements, creating a feature spec, or preparing a product brief. Triggers: PRD, product requirements, feature spec, product brief, requirements document."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
# Create a Product Requirements Document
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: dummy-dataset
|
||||
description: "Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, generating sample datasets, or building realistic mock data for development. Triggers: dummy data, test data, mock dataset, sample data, generate data."
|
||||
description: "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."
|
||||
---
|
||||
# Dummy Dataset Generation
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: job-stories
|
||||
description: "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, expressing user situations and motivations, or creating JTBD-style backlog items. Triggers: job stories, JTBD story, situation motivation outcome."
|
||||
description: "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."
|
||||
---
|
||||
# Job Stories
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: outcome-roadmap
|
||||
description: "Transform an output-focused roadmap into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting from output to outcome roadmaps, rewriting a feature roadmap, or making a roadmap more strategic. Triggers: outcome roadmap, outcome-focused, rewrite roadmap, strategic roadmap, outcome statements."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
# Transform Roadmap to Outcome-Focused Format
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: pre-mortem
|
||||
description: "Run a pre-mortem analysis on a PRD. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies Tigers as launch-blocking, fast-follow, or track. Use when preparing for launch, risk-assessing a PRD, or stress-testing a product plan. Triggers: pre-mortem, launch risks, what could go wrong, risk analysis PRD, stress test plan."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
# Pre-Mortem: Risk Analysis for Product Launch
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: prioritization-frameworks
|
||||
description: "Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates. Covers Opportunity Score, ICE, RICE, Kano, MoSCoW, and more. Use when selecting a prioritization method, comparing frameworks, or needing formula definitions. Triggers: prioritization framework, which framework, ICE, RICE, opportunity score, Kano, MoSCoW, how to prioritize."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
## Prioritization Frameworks Reference
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: release-notes
|
||||
description: "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 a release. Triggers: release notes, changelog, what's new, product update, release announcement, ship notes."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
## Release Notes Generator
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: retro
|
||||
description: "Facilitate a structured sprint retrospective. Analyzes what went well, what didn't, and generates prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, or creating action items from team feedback. Triggers: retro, retrospective, sprint retro, what went well, lessons learned, team reflection."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
## Sprint Retrospective Facilitator
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: sprint-plan
|
||||
description: "Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories for a sprint, or balancing sprint scope. Triggers: sprint plan, sprint planning, capacity planning, sprint scope, what fits in the sprint, story points."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
## Sprint Planning
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: stakeholder-map
|
||||
description: "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. Triggers: stakeholder map, stakeholder analysis, power interest grid, stakeholder management, communication plan, who to align."
|
||||
description: "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 Mapping & Communication Plan
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: summarize-meeting
|
||||
description: "Summarize a meeting transcript into a structured template with date, participants, topic, summary points, and action items. Use when processing meeting recordings, creating meeting notes, or summarizing any internal meeting. Triggers: summarize meeting, meeting notes, meeting summary, meeting minutes, recap meeting."
|
||||
description: "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."
|
||||
---
|
||||
|
||||
# Summarize Meeting
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: test-scenarios
|
||||
description: "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, or defining acceptance tests. Triggers: test scenarios, test cases, QA scenarios, acceptance tests."
|
||||
description: "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."
|
||||
---
|
||||
# Test Scenarios
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: user-stories
|
||||
description: "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, or creating backlog items. Triggers: user stories, backlog story, acceptance criteria."
|
||||
description: "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."
|
||||
---
|
||||
# User Stories
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: wwas
|
||||
description: "Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context. Use when writing backlog items or breaking features into work items. Triggers: WWA, why what acceptance, backlog items, work items."
|
||||
description: "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."
|
||||
---
|
||||
# Why-What-Acceptance (WWA)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user