mirror of
https://github.com/phuryn/pm-skills.git
synced 2026-06-11 22:14:56 +03:00
Pawel Huryn
43 lines
3.5 KiB
Markdown
43 lines
3.5 KiB
Markdown
# pm-execution
|
||
|
||
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
|
||
|
||
## Skills (15)
|
||
|
||
- **brainstorm-okrs** — Brainstorm team-level OKRs aligned with company objectives.
|
||
- **create-prd** — Create a Product Requirements Document using a comprehensive 8-section template covering summary, background, objectives, market segments, value propositions, solution details, and release planning.
|
||
- **dummy-dataset** — Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script).
|
||
- **job-stories** — Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria.
|
||
- **outcome-roadmap** — Transform an output-focused roadmap into an outcome-focused one.
|
||
- **pre-mortem** — Run a pre-mortem analysis on a PRD.
|
||
- **prioritization-frameworks** — Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates.
|
||
- **release-notes** — Generate user-facing release notes from tickets, PRDs, or changelogs.
|
||
- **retro** — Facilitate a structured sprint retrospective.
|
||
- **sprint-plan** — Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.
|
||
- **stakeholder-map** — Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.
|
||
- **summarize-meeting** — Summarize a meeting transcript into a structured template with date, participants, topic, summary points, and action items.
|
||
- **test-scenarios** — Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
|
||
- **user-stories** — Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
|
||
- **wwas** — Create product backlog items in Why-What-Acceptance format.
|
||
|
||
## Commands (10)
|
||
|
||
- `/pm-execution:generate-data` — Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts.
|
||
- `/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: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.
|
||
|
||
## Author
|
||
|
||
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
|
||
|
||
## License
|
||
|
||
MIT
|