Strategy Document
Turn fuzzy business decisions into falsifiable SWOTs, lean plans, OKRs, or competitive analyses your agent can execute on next.
Overview
Strategy Document Writer is an agent skill most often used in Validate (also Idea research, Grow analytics) that drafts SWOT analyses, lean business plans, OKRs, and competitive analyses with falsifiable, actionable deta
Install
npx skills add https://github.com/jezweb/claude-skills --skill strategy-documentWhat is this skill?
- Four document modes: SWOT, business plan (lean or full), OKRs/goals, and competitive analysis
- Two-step workflow: pick mode from the decision you need, then gather business context before drafting
- Quality bar: falsifiable statements and recommendations with defined timeframes
- Decision router maps prompts like funding, market entry, and quarterly focus to the right mode
- Produces actionable documents rather than generic strategy frameworks
- 4 document modes
- 2-step process with decision router
Adoption & trust: 649 installs on skills.sh; 841 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to articulate strategy or goals but only have vague bullet points that no one can act on or test.
Who is it for?
Solo founders and small teams deciding market entry, quarterly focus, funding narrative, or competitive positioning before committing engineering time.
Skip if: Skip when you already have an approved, dated strategy pack and only need formatting tweaks—or when you want legal/financial advice instead of structured planning prose.
When should I use this skill?
Use whenever a business asks to articulate strategy, set goals, analyse competition, plan for growth, do a SWOT, write OKRs, or build a lean business plan.
What do I get? / Deliverables
You get a structured strategic document with measurable OKRs or clear competitive positioning you can hand to implementation, fundraising, or roadmap planning.
- SWOT, business plan, OKR set, or competitive analysis document
- Mode-specific sections with actionable recommendations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because most installs happen when a solo builder is scoping what to build, fund, or focus on before heavy implementation. Scope subphase matches OKRs, lean plans, and quarterly focus—not vanity decks—after idea-stage research may already exist.
Where it fits
Map direct and indirect competitors before committing to a niche feature set.
Draft a lean business plan to bound MVP scope and revenue assumptions.
Use competitive analysis output to sanity-check positioning and price bands.
Set quarterly OKRs tied to measurable activation or retention targets.
How it compares
Use instead of asking the agent for a generic SWOT template without context gathering or falsifiability rules.
Common Questions / FAQ
Who is strategy-document for?
Solo builders, indie SaaS founders, and small business operators who want agent-guided SWOTs, OKRs, lean plans, or competitive analyses without hiring a strategy consultant.
When should I use strategy-document?
Use it in Validate when scoping a product or quarter; in Idea when researching competitors or market entry; and in Grow when setting measurable OKRs—especially before funding decks or major roadmap bets.
Is strategy-document safe to install?
It is prose and process guidance with no built-in shell or network tools; review the Security Audits panel on this Prism page before trusting any third-party skill in your agent environment.
SKILL.md
READMESKILL.md - Strategy Document
# Strategy Document Writer Produces strategic documents that are specific enough to act on. The quality bar: every statement should be falsifiable ("We have 3 React developers with 10+ years experience" vs "We have a strong team") and every recommendation should be implementable within a defined timeframe. ## Process ### Step 1: Determine the mode Ask the user which document type they need: 1. **SWOT analysis** — assess current position 2. **Business plan** (lean or full) — articulate the business model 3. **OKRs / Goals** — set measurable objectives 4. **Competitive analysis** — understand the market landscape If the user is unsure, ask what decision they are trying to make. That usually reveals the right mode: - "Should we enter this market?" -> Competitive analysis + SWOT - "What should we focus on this quarter?" -> OKRs - "We need funding / a partner deck" -> Business plan - "Something feels off but I can't pinpoint it" -> SWOT ### Step 2: Gather context Ask for: - Business name, industry, size (team, revenue if comfortable sharing) - Current situation (what prompted this exercise?) - Key competitors (if known) - Time horizon (this quarter, this year, 3-year) - Audience for the document (internal team, board, investors, bank, personal clarity) The audience determines the level of detail. A bank wants financial projections. A founder wants clarity. A team wants direction. ### Step 3: Draft and validate Write the document, then review every entry against the specificity test: could this statement apply to any business in the industry? If yes, it is too vague. Rewrite with the user's specific context. --- ## Mode 1: SWOT Analysis ### Structure Present as a 2x2 grid with 3-5 points per quadrant. Each point is one sentence — specific and actionable. ``` HELPFUL HARMFUL to achieving objectives to achieving objectives INTERNAL STRENGTHS WEAKNESSES (origin) - ... - ... - ... - ... EXTERNAL OPPORTUNITIES THREATS (origin) - ... - ... - ... - ... ``` **Internal** (Strengths, Weaknesses) = things the business controls: team skills, processes, technology, finances, culture, IP. **External** (Opportunities, Threats) = things the business does not control: market trends, competitors, regulation, economic conditions, technology shifts. ### Quality bar for entries | Too vague | Specific and useful | |-----------|-------------------| | "Strong team" | "3 developers with 10+ years React experience; only 1 has backend skills" | | "Good reputation" | "4.8 Google rating from 127 reviews; 94% client retention over 3 years" | | "Growing market" | "Australian SME SaaS market growing 12% annually (IBISWorld 2025)" | | "Competition" | "Competitor X launched a free tier in Q4 2025, capturing 200+ of our target segment" | | "Cash flow issues" | "Average debtor days: 58; target: 30. $120K outstanding beyond 60 days" | Every entry should pass the "so what?" test — it must be clear why this point matters for strategic decisions. ### The "So What?" Section After the grid, add a section that translates findings into actions: **Strategic implications:** - Which strengths can be leveraged against which opportunities? (attack) - Which weaknesses are exposed by which threats? (defend) - What should the business start doing, stop doing, or change? This is the most valuable part of a SWOT. The grid without implications i