fix(skills): add Anti-Patterns sections, fix descriptions, quality checks, and required inputs
- 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:
@@ -54,3 +54,11 @@ Ask the user for these if not provided:
|
||||
- [ ] Progression narrative shows causal links between quarters (not just chronological listing)
|
||||
- [ ] "What's not on the roadmap" section includes at least 2 items with clear rationale
|
||||
- [ ] Language throughout is free of engineering jargon — tested by asking: "could a CFO repeat this?"
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not produce a list of features with dates and call it a narrative — every initiative must connect to a strategic theme
|
||||
- [ ] Do not omit the "what's not on the roadmap" section — without it, the narrative lacks strategic discipline
|
||||
- [ ] Do not write progression as a chronological list — show causal links between quarters (Q1 enables Q2 because…)
|
||||
- [ ] Do not write the executive summary last and treat it as a summary — write it as the version stakeholders will repeat
|
||||
- [ ] Do not let orphaned initiatives appear without a theme — either create a theme or flag the gap explicitly
|
||||
|
||||
Reference in New Issue
Block a user