fix(skills): add Anti-Patterns and fix descriptions for remaining skills (batch 3)
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:
@@ -122,6 +122,14 @@ Testing is complete when:
|
||||
- [ ] Each test type names a concrete tool (not "some testing framework")
|
||||
- [ ] Definition of Done is measurable (not "tests are done when QA is happy")
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not write a test strategy without a risk table that drives test priority — generic coverage targets are not a strategy
|
||||
- [ ] Do not leave the "out of scope" section blank — every test strategy must explicitly name what is not being tested and why
|
||||
- [ ] Do not specify test types without naming a concrete tool for each — "some testing framework" is not actionable
|
||||
- [ ] Do not define a Definition of Done that is not measurable — "QA is happy" is not a completion criterion
|
||||
- [ ] Do not create P0 risk areas without corresponding P0 test cases — risk rating must map to test coverage
|
||||
|
||||
## Usage Examples
|
||||
- "Write a test strategy for [feature]" + [paste spec or PRD]
|
||||
- "Create a test plan for [system]"
|
||||
|
||||
Reference in New Issue
Block a user