feat: 100 skills milestone — 7 new skills + quality improvements across all 93

New skills added:
- teaching-lesson-plan: structured lesson plans for any subject/audience/setting
- seo-content-brief: complete SEO briefs with intent, competitor gaps, and outline
- media-pitch: story-first journalist pitches with angle development framework
- change-management-plan: stakeholder analysis, comms strategy, adoption metrics
- workshop-facilitation-guide: activity instructions, decision protocols, facilitator moves
- sales-forecasting-model: pipeline model, scenario analysis, assumption log
- tax-planning-checklist: year-end tax planning across income, pension, CGT, reliefs

Quality improvements across all 93 existing skills:
- Standardised description format: "Verb the thing. Use when X. Produces Y."
- Added Required Inputs section to all skills missing it (prompts for missing info)
- Added Quality Checks section to all skills missing it (specific, not generic)
- Fixed broken multiline YAML descriptions
- Removed non-standard frontmatter keys (tool_integration, metadata blocks)

README updated to v6.0.0 with 100-skill count, new skill tables, and article series

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

skills/roadmap-narrative/SKILL.md

@@ -1,21 +1,29 @@
 ---
 name: roadmap-narrative
-description: Transform a prioritised initiative list into a compelling strategic roadmap narrative
-tool_integration: Notion, Miro
+description: "Transform a prioritised initiative list into a compelling strategic roadmap narrative. Use when asked to write a roadmap narrative, explain the product roadmap to non-technical stakeholders, connect roadmap items to company goals, or produce an exec-shareable roadmap story. Produces a themed narrative with strategic context, quarter progression arc, an executive summary, and a 'what's not on the roadmap' section."
 ---
+
 # Roadmap Narrative Skill
 
-## Purpose
 Convert a ranked list of product initiatives into a clear, strategic narrative that connects individual items to company goals and communicates a coherent product direction.
 
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Prioritised initiative list** (with rough timelines or quarters)
+- **Company OKRs or strategic priorities** (to connect roadmap to company goals)
+- **Audience** (all-hands, board, investors, sales team — changes tone and depth)
+- **Items explicitly NOT on the roadmap** (optional but strengthens credibility)
+
 ## Process
 1. Review the prioritised initiative list and company OKRs provided
 2. Identify 2-3 strategic themes that group the initiatives naturally
 3. For each theme, articulate: the problem it addresses, the customer it serves, the metric it moves
 4. Write a quarter-level narrative that shows progression — how does H1 set up H2?
 5. Draft an executive summary (3-4 sentences max) that non-technical stakeholders can repeat
+6. **Validate** — Confirm every initiative maps to a theme. If an initiative is orphaned, either create a theme or flag it as a narrative gap to address
 
-## Output Format
+## Output Structure
 
 ### Product Roadmap: [Quarter/Half/Year]
 **Strategic Context:** [1 paragraph: market moment, key challenge, our response]
@@ -28,10 +36,21 @@ Convert a ranked list of product initiatives into a clear, strategic narrative t
 
 [Repeat for each theme]
 
+**What's Not on the Roadmap (and Why):**
+[2-3 items with rationale — shows strategic discipline, not just prioritisation]
+
 **Executive Summary (shareable):**
 [3-4 sentences that could be shared in an all-hands or board update]
 
 ## Tone Guidelines
-- Avoid jargon — write for a CFO, not an engineer
+- Write for a CFO, not an engineer
 - Lead with customer outcomes, not features
 - Be honest about what's NOT on the roadmap and why
+
+## Quality Checks
+
+- [ ] Every initiative in the input maps to a strategic theme
+- [ ] The executive summary can stand alone and be repeated correctly after one reading
+- [ ] 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?"