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 3)

Browse Source 
Processed 27 skills: teaching-lesson-plan through feature-prioritisation and all figma skills.
Added Anti-Patterns sections to all 27 skills.
Added Quality Checks section to financial-due-diligence (was missing entirely).
Converted user-research-synthesis Quality Standards to binary checkbox format.
Rewrote descriptions for figma-design-critique-pm, figma-design-qa, figma-design-review,
team-health-check, and user-interview-synthesis.

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 13:01:36 +00:00
parent f170eed437
commit fb85a1cb55
27 changed files with 234 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/team-health-check/SKILL.md
+9 -1
View File
@@ -1,6 +1,6 @@
---
name: team-health-check
description: "Run a structured team health assessment. Use when asked to run a team health check, assess team morale, facilitate a team retrospective on ways of working, or evaluate team dynamics. Produces a health assessment across key dimensions with RAG status, underlying signals, and prioritised improvement actions."
description: "Runs a structured team health assessment across key dimensions. Use when asked to run a team health check, assess team morale, facilitate a retrospective on ways of working, or evaluate team dynamics. Produces a health assessment with RAG status per dimension, underlying signals, and prioritised improvement actions with named owners."
---
# Team Health Check Skill
@@ -253,6 +253,14 @@ Use this template to document results after the session or survey.
- [ ] Results are shared with the team, not kept by management
- [ ] Trend data is tracked across cycles to show improvement or regression
## Anti-Patterns
- [ ] Do not run a health check without first establishing psychological safety — without it, scores reflect fear, not reality
- [ ] Do not treat a single health check as a trend — one data point cannot show improvement or regression
- [ ] Do not keep results with management without sharing them with the team — transparency is a prerequisite for trust
- [ ] Do not generate action items that are vague commitments like "improve communication" — every action must be specific and verifiable
- [ ] Do not assign actions to "the team" — each improvement action needs a single named owner
## Example Trigger Phrases
- "Run a team health check for my engineering squad"