plugins/ce/skills/strategy-writer/SKILL.md
Produces executive-quality strategic documents in The Economist/HBR style. Use when writing strategy memos, market analysis, business cases, customer research reports, or any document for Product, Design, and Business leaders. Customer-led, evidence-based, narrative-driven.
npx skillsauth add rileyhilliard/claude-essentials strategy-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Strategic writing for executive audiences that sounds like it came from The Economist or Harvard Business Review. Customer-led thinking, evidence-based arguments, cohesive narrative.
| Writing... | Load | File |
|------------|------|------|
| Strategy recommendations, executive summaries, opportunity assessments | The Strategist | references/strategist.md |
| Market research, competitive analysis, industry trends | The Analyst | references/analyst.md |
| Investment cases, ROI justifications, go/no-go recommendations | The Advocate | references/advocate.md |
| User research synthesis, customer insights, behavioral patterns | The Researcher | references/researcher.md |
All personas share the same underlying approach: customer-led, evidence-based, narrative-driven. The difference is framing and structure, not rigor.
Frame every argument from the customer's perspective first. Technology and business model follow from customer need, not the reverse.
Every significant claim needs backing. Data, research, examples, or logical reasoning. "We believe" is not evidence.
Ideas should flow logically from one to the next. The reader should feel the argument building. Isolated points, no matter how valid, don't persuade.
Move from problem to insight to implication to recommendation. Don't jump around. Don't bury the lead, but do earn the conclusion.
Ambitious framing is fine. Excitement about opportunity is fine. But ground it in reality. The reader should feel possibility, not skepticism.
See references/forbidden-patterns.md for shared patterns (em dashes, buzzwords, hedging, emojis).
Strategy-specific:
Wrong: "AI enables us to..." Right: "Customers struggle with X. AI is one way to address this because..."
Lead with the problem and the person experiencing it.
Wrong: "The market is ready for this." Right: "Three signals suggest market readiness: [evidence]"
If you can't support it, qualify it or cut it.
Every point the user requests must appear in the final output. Do not summarize away, merge, or skip details from the prompt.
Extract all discrete points, requirements, and topics from the user's request. Create a mental checklist.
As you write, track which points you've addressed. If a point doesn't fit the narrative flow, find a place for it anyway. Cohesion matters, but completeness matters more.
Review the output against the original request. Verify every requested element is present. If something is missing, add it before delivering.
The user included them for a reason. Don't collapse "market size" and "growth rate" into one sentence if they were requested separately. Give each point its due space.
Long prompts are not invitations to summarize. They're specifications. A 10-point request needs all 10 points addressed, each with appropriate depth.
| Source Type | Use For | Credibility | |-------------|---------|-------------| | Primary data (interviews, surveys, analytics) | Core claims | Highest | | Peer-reviewed research, industry reports (Gartner, McKinsey) | Market context, trends | High | | Reputable journalism (Economist, FT, WSJ) | Current events, examples | Medium-high | | Company reports, press releases | Company-specific facts | Medium (biased) | | Blog posts, social media | Anecdotes, signals | Low (corroborate) |
External documents (board decks, investor materials, published reports): Cite sources explicitly. Include enough detail for readers to verify.
Internal strategy docs: Lighter touch. Reference data sources but don't need formal citations. Focus on making the logic auditable.
| Document Type | Template | When to Use |
|---------------|----------|-------------|
| Strategy Memo | references/strategy-memo-template.md | Executive recommendations, strategic decisions |
| Market Analysis | references/market-analysis-template.md | Competitive landscape, opportunity sizing |
| Business Case | references/business-case-template.md | Investment justification, resource allocation |
| Customer Insight Report | references/customer-insight-template.md | Research synthesis, user behavior patterns |
Load The Strategist when:
Load The Analyst when:
Load The Advocate when:
Load The Researcher when:
development
Selects and applies professional journalistic story structures (WSJ Formula, Inverted Pyramid, Hourglass, Tick-Tock, etc.) based on the content being written. Use when writing articles, blog posts, features, essays, long-form content, news stories, trend pieces, investigative reports, profiles, or any narrative prose longer than a few paragraphs. Also use when the user asks for help structuring a piece, choosing a story framework, organizing a draft, outlining an article, or wants to know which article format fits their content. Trigger on requests like "help me structure this," "what format should I use," "write a feature about," "draft a blog post on," or any mention of story structure, article architecture, or narrative frameworks. Complements the writer skill (which handles tone and anti-AI rhetoric) by providing the structural blueprint.
testing
Writing style and tone guide for human-sounding content. Use when writing documentation, READMEs, commit messages, PR descriptions, blog posts, LinkedIn posts, social media content, or any user-facing content.
data-ai
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
development
Debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.