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

fix(skills): add Anti-Patterns and fix descriptions for remaining skills (batch 2)

Browse Source 
Processed 24 skills: pr-description-writer through tax-planning-checklist.
Added Anti-Patterns sections to all 24 skills.
Added Required Inputs section to product-launch-checklist.
Rewrote descriptions for retro-analysis, substack-notes-scraper, and sycophancy-challenger.

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 12:57:05 +00:00
parent a33b4f7003
commit f170eed437
24 changed files with 204 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/retro-analysis/SKILL.md
+9 -1
View File
@@ -1,6 +1,6 @@
---
name: retro-analysis
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."
description: "Analyses sprint delivery data and produces 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
@@ -51,3 +51,11 @@ Ask the user for these if not provided:
- [ ] 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?)
## Anti-Patterns
- [ ] Do not assign blame to individuals in the retrospective brief — observations must describe patterns, not people
- [ ] Do not produce Start/Stop/Continue prompts that are vague categories — each must name a specific behaviour
- [ ] Do not recommend an experiment that cannot be completed within one sprint — small, testable experiments only
- [ ] Do not treat carry-over tickets as a velocity problem without first identifying the root cause category
- [ ] Do not run the same retrospective format every sprint — vary the format to prevent engagement fatigue