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

fix(skills): add Anti-Patterns sections, fix descriptions, quality checks, and required inputs

Browse Source 
- Add Anti-Patterns section (3-5 binary checkboxes) to all modified skills
- Fix Quality Checks to use binary checkbox format where needed
- Rewrite descriptions to verb-when-produces format where needed
- Add Required Inputs sections to skills missing them
- Fix email-triage frontmatter YAML quoting

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 10:20:50 +00:00
parent 44f69a541f
commit 4ff88bdbb1
88 changed files with 740 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/roadmap-presentation/SKILL.md
+8
View File
@@ -128,3 +128,11 @@ Every roadmap needs a narrative, not just a timeline. Structure it as:
- [ ] "What We're NOT Building" section has at least 2 items with rationale
- [ ] Success metrics are specified per theme (not just a list of features)
- [ ] Language is free of internal jargon — tested by asking: "could an external stakeholder understand this?"
## Anti-Patterns
- [ ] Do not put specific dates on NEXT or LATER items — use quarters or halves to signal appropriate confidence levels
- [ ] Do not show the same level of detail to executives and engineers — calibrate depth to audience or you lose both
- [ ] Do not omit the "What We're NOT Building" section — a roadmap without explicit deprioritisation becomes a wish list
- [ ] Do not present LATER items as commitments — frame everything outside NOW as directional, not promised
- [ ] Do not skip the success metrics section — without it, stakeholders cannot evaluate whether the roadmap is working