justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: sync all skill updates and new skills into plugin bundles

Browse Source 
- Synced 97 existing skill SKILL.md files from skills/ to their plugin bundle copies
- Added 7 new skills to plugin bundles:
  - seo-content-brief, media-pitch -> pm-gtm
  - tax-planning-checklist -> pm-finance
  - change-management-plan -> pm-hr
  - sales-forecasting-model -> pm-sales
  - workshop-facilitation-guide -> pm-operations
  - teaching-lesson-plan -> pm-cross

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mohitagw15856
2026-04-20 21:00:00 +01:00
parent d7f6c2cd05
commit 513e1d3ce7
67 changed files with 1851 additions and 507 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/pm-delivery/skills/retro-analysis/SKILL.md
+23 -13
View File
@@ -1,19 +1,20 @@
---
name: retro-analysis
description: Analyse sprint delivery data and produce a structured retrospective brief
tool_integration: Jira, Miro
description: "Analyse sprint delivery data and produce a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint."
---
# Retrospective Analysis Skill
## Purpose
Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened.
## Required Inputs
- Sprint tickets: planned vs. completed
- Carry-over tickets and reasons
- Tickets reopened after closing
- Any incidents or unplanned work
- Sprint velocity vs. historical average
Ask the user for these if not provided:
- **Sprint tickets: planned vs. completed**
- **Carry-over tickets and reasons** (if known)
- **Tickets reopened after closing** (quality signal)
- **Any incidents or unplanned work** (scope creep signal)
- **Sprint velocity vs. historical average** (trend context)
## Process
1. Calculate: completion rate, carry-over rate, unplanned work percentage
@@ -21,8 +22,9 @@ Generate a data-grounded retrospective brief that separates facts from feelings,
3. Note any process or communication breakdowns visible in the data
4. Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint
5. Suggest 1 concrete experiment for the next sprint based on the biggest friction point
6. **Validate** — Confirm each prompt is specific to this sprint (not a recycled generic prompt), and that the recommended experiment is concrete and measurable
## Output Format
## Output Structure
### Sprint [Number] Retrospective Brief
@@ -35,9 +37,17 @@ Generate a data-grounded retrospective brief that separates facts from feelings,
[2-3 observations grounded in the numbers above]
**Discussion Prompts:**
- Start: [specific prompt]
- Stop: [specific prompt]
- Continue: [specific prompt]
- Start: [specific prompt based on this sprint's data]
- Stop: [specific prompt based on this sprint's data]
- Continue: [specific prompt based on this sprint's data]
**Suggested Experiment for Next Sprint:**
[One concrete, testable process change]
[One concrete, testable process change — with a specific success metric]
## Quality Checks
- [ ] Each Start/Stop/Continue prompt names a specific behaviour, not a vague category
- [ ] The recommended experiment is testable in one sprint
- [ ] Carry-over analysis identifies the ticket type or cause, not just the count
- [ ] Data observations don't assign blame — they describe patterns
- [ ] Velocity trend is mentioned in context (is this a one-off or a pattern?)