Agent skill

Strategy Document

by jezweb in jezweb/claude-skills

Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses.

MITAuto-check passedBusiness, Finance & HR

Install Strategy Document

skills CLI
$ npx skills add jezweb/claude-skills --skill strategy-document -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jezweb/claude-skills strategy-document --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/writing/skills/strategy-document .claude/skills/strategy-document && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
strategy-document
GitHub stars
1.1k
Token cost
~3k tokens
SKILL.md length
1,536 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses.

  • Works in 3 steps: Determine the mode → Gather context → Draft and validate
  • A business asks to articulate strategy
  • SKILL.md covers Process, Mode 1: SWOT Analysis, Mode 2: Business Plan and Mode 3: OKRs and Goals, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Strategy Document is an agent skill from jezweb/claude-skills. Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses. Each mode has a defined structure and quality bar. 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. Produces actionable documents, not generic frameworks.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR, covering Startup and business strategy and OKRs and executive reporting. The repository describes itself as: Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.

When your agent uses it

  • A business asks to articulate strategy
  • Analyse competition
  • Plan for growth
  • Build a lean business plan

Example prompts

  • “/strategy-document”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Determine the mode
  2. Gather context
  3. Draft and validate

What it can do on your machine

Read from SKILL.md and the folder at commit 64965d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Strategy Document loads about 3k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 1,536 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jezweb/claude-skills at commit 64965d9, republished under its MIT licence (© jezweb). 1,536 words, ~2,964 tokens.

Download SKILL.mdSave it as .claude/skills/strategy-document/SKILL.md (or your agent's skills folder).
name
strategy-document
description
Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses. Each mode has a defined structure and quality bar. 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. Produces actionable documents, not generic frameworks.

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 vagueSpecific 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 is an exercise in categorisation, not strategy.

Anti-patterns
  • Listing the same point in both Strengths and Opportunities (if it is internal, it is a strength)
  • Including items the business cannot influence in Strengths/Weaknesses
  • Generic entries that apply to every business in the industry
  • No implications section — the grid alone is not actionable

Mode 2: Business Plan

Lean format (one page)

Use when the audience is the founder or a small team needing clarity. One paragraph per section, no padding.

SectionWhat to write
ProblemWhat pain exists? Who feels it? How do they cope today?
SolutionWhat does the business offer? In one sentence.
Key Metrics3-5 numbers that indicate health (MRR, churn, CAC, LTV, NPS)
Unique Value PropWhy this business over alternatives? One sentence.
ChannelsHow do customers find you? Rank by effectiveness.
Revenue StreamsHow does money come in? List each stream with approximate % of total.
Cost StructureTop 5 cost categories with approximate monthly/annual figures.
Unfair AdvantageWhat cannot be easily copied? (team expertise, proprietary data, network effects, regulatory position)

The test for each section: if you cannot say it in one paragraph, you do not understand it well enough yet. Rewrite until you can.

Full format

Adds to the lean format:

  • Executive Summary (write last — it summarises everything else)
  • Market Analysis — TAM/SAM/SOM with sources, customer segments, market trends
  • Financial Projections — 12-month P&L, cash flow forecast, break-even analysis
  • Team — key people, their relevant experience, gaps to fill
  • Milestones — what happens in the next 3, 6, and 12 months with specific deliverables
Writing principles for plans
  • Present tense for current state, future tense for plans. Never past tense for the core model.
  • Financial projections must state assumptions explicitly. "$50K MRR by month 12" needs "assuming 15% monthly growth from current $12K base and 5% churn."
  • Acknowledge risks. Investors and lenders trust founders who see the dangers, not those who pretend they do not exist.
  • No aspirational filler. "We aim to be the leading provider" is not a plan. "We will acquire 200 paying customers in 12 months through Google Ads ($5K/month budget, target $25 CAC)" is a plan.

Mode 3: OKRs and Goals

Structure
OBJECTIVE: [Qualitative, inspiring, time-bound]

  KR1: [Quantitative, measurable, has a number]
  KR2: [Quantitative, measurable, has a number]
  KR3: [Quantitative, measurable, has a number]

Typically 3-5 Objectives per quarter, each with 3-5 Key Results.

Objectives
  • Qualitative and inspiring — describes the desired future state
  • Time-bound (usually one quarter)
  • Ambitious but achievable with stretch effort (70% completion = healthy)
Too vagueSpecific
"Improve our marketing""Establish a predictable inbound lead pipeline by end of Q2"
"Grow the business""Expand into the Brisbane market with a repeatable sales process by Q3"
"Be more efficient""Eliminate manual reporting bottlenecks across all client accounts by Q2"
Show full SKILL.md (653 more words)Show less
Key Results
  • Quantitative with a specific target number
  • Measurable — you can check at quarter end whether it was achieved
  • Outcomes, not tasks
Task (wrong)Outcome (right)
"Launch the new website""Achieve 1,000 monthly organic visitors to the new site"
"Hire 2 developers""Reduce average feature delivery time from 3 weeks to 1 week"
"Run Google Ads campaign""Generate 50 qualified leads at under $30 CAC"
"Write 12 blog posts""Grow organic traffic 40% (800 to 1,120 monthly sessions)"

Tasks are the activities you do to achieve Key Results. They belong on a project plan, not in OKRs.

Scoring

At quarter end, score each KR from 0.0 to 1.0:

  • 0.0-0.3: Failed to make meaningful progress
  • 0.4-0.6: Made progress but fell short
  • 0.7-0.9: Delivered strong results (this is the target zone)
  • 1.0: Hit the target exactly (may indicate the target was too easy)

If every OKR scores 1.0, the goals were not ambitious enough. If every OKR scores below 0.3, they were unrealistic or the wrong priorities.


Mode 4: Competitive Analysis

Structure

Start with a comparison matrix, then interpret it.

Comparison matrix:

FactorYour BusinessCompetitor ACompetitor BCompetitor C
Price point$X/mo$Y/mo$Z/moFree tier + $W/mo
Key feature 1YesYesNoPartial
Key feature 2NoYesYesYes
Target marketAU SMEsEnterpriseStartupsAll segments
StrengthPersonal serviceScalePriceBrand recognition
WeaknessSmall teamImpersonalLimited featuresSlow support
Interpretation sections

Where you win: Specific advantages with evidence. "Faster onboarding (3 days vs industry average of 2 weeks)" not "better service".

Where you lose: Honest assessment. "Competitor A has 10x our development team; we cannot match their feature velocity" is more useful than pretending the gap does not exist.

Where you differentiate: What you do that others structurally cannot or choose not to. This is the strategic gold — it informs positioning, messaging, and product decisions.

Recommended actions: Based on the analysis, what should change? New features to build, segments to target or avoid, pricing adjustments, partnership opportunities.

Research sources
  • Competitor websites (pricing pages, feature lists, case studies)
  • Review sites (G2, Capterra, Google Reviews, ProductHunt)
  • Job listings (reveal their priorities and gaps)
  • Social media and content (positioning, audience, tone)
  • Industry reports (market size, growth rates, trends)

If the user has access to competitors' actual customers (through industry networks, forums, social media), first-hand feedback is more valuable than any published report.


Writing Principles (All Modes)

Specific over vague. Every claim needs a number, a name, or a concrete example. "Strong growth" is not strategy — "40% revenue increase from $850K to $1.19M" is strategy.

Evidence over opinion. "We believe the market is growing" vs "The AU SaaS market grew 12% in 2025 (source)." If you cannot find evidence, say so — an honest gap is better than a fabricated claim.

Actionable over aspirational. Every section should answer "what do we do with this information?" If a SWOT entry or competitive insight does not lead to a decision or action, it is not worth including.

Honest about weaknesses. Strategy documents that only list strengths are useless. The value is in seeing the full picture — including the uncomfortable parts. Investors, partners, and teams all trust honesty more than polish.

Appropriate length. A lean business plan is one page. A SWOT is one page plus implications. OKRs are a few pages at most. Competitive analysis scales with the number of competitors. Do not pad for length — every sentence must earn its place.

Example: SWOT Strength Entry

Too vague:

Strong digital presence and good online reputation.

Right approach:

4.8 average Google rating from 127 reviews (highest among Newcastle web agencies). Website generates 35 qualified leads per month organically, with a 12% conversion rate to paying clients. Social media following of 2,400 across LinkedIn and Instagram, with 6.2% average engagement rate on case study posts.

The second version gives the reader three data points they can compare against competitors, benchmark against industry averages, and track over time.

© jezweb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/writing/skills/strategy-document of jezweb/claude-skills.

Open the folder on GitHubat commit 64965d9

Compare with similar skills

Strategy Document next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Strategy Document compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Strategy Document this skilljezweb/claude-skills1.1k—~3kAutomated safety check: PassMIT
Product Strategistdavila7/claude-code-templates32k3 repos~248Automated safety check: PassMIT
Space Chart HTML PlusSpaceZephyr/design-buddy174—~1.6kAutomated safety check: PassNone
Startup Metricsguia-matthieu/clawfu-skills150—~5kAutomated safety check: PassMIT
Partnerships EcosystemLeoYeAI/openclaw-master-skills2.2k—~5kAutomated safety check: PassMIT
Strategic Planningw95/awesome-claude-corporate-skills235—~2.2kAutomated safety check: PassMIT

Similar skills

  • Product Strategist

    davila7/claude-code-templates

    Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling.

    32k GitHub starsUsed in 3 repos~248 tokens
    Business, Finance & HRAuto-check passed
  • Space Chart HTML Plus

    SpaceZephyr/design-buddy

    AI 全能图表生成器(扩展版)。一键生成 35+ 种设计美观的图表 HTML 文件,涵盖技术架构、流程逻辑、业务战略、数据可视化、信息展示 5 大类别。支持 3 种内置视觉风格(黑白简约、深色暗调、Claude 暖色)+ 品牌风格扩展。

    174 GitHub stars~1.6k tokensUpdated 3 mo ago
    Business, Finance & HRAuto-check passed
  • Startup Metrics

    guia-matthieu/clawfu-skills

    Know the metrics that matter at each stage and what investors actually look for.

    150 GitHub stars~5k tokensUpdated 6 days ago
    Business, Finance & HRAuto-check passed
  • Partnerships Ecosystem

    LeoYeAI/openclaw-master-skills

    World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~5k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • Strategic Planning

    w95/awesome-claude-corporate-skills

    ACTIVATE when developing long-term strategy, setting OKRs, creating vision statements, building SWOT analyses, designing strategic frameworks, defining company direction, planning multi-year…

    235 GitHub stars~2.2k tokensUpdated 7 mo ago
    Business, Finance & HRAuto-check passed
  • Strategy Framework

    revfactory/harness-100

    A full pipeline that systematizes an organization's strategy framework through OKR design, BSC mapping, SWOT analysis, vision & mission statement, and strategy execution roadmap.

    1.3k GitHub stars~2k tokensUpdated 6 mo ago
    Business, Finance & HRAuto-check passed

More from jezweb/claude-skills

All 52 skills in this repo
  • Elevenlabs Agents

    jezweb/claude-skills

    Build conversational AI voice agents on the ElevenLabs platform.

    1.1k GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed
  • Favicon Gen

    jezweb/claude-skills

    Generate custom favicons from logos, text, or brand colours.

    1.1k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Tailwind Theme Builder

    jezweb/claude-skills

    Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.

    1.1k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Responsiveness Check

    jezweb/claude-skills

    Test website responsiveness across viewport widths using browser automation.

    1.1k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • MCP Builder

    jezweb/claude-skills

    Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.

    1.1k GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check: notes
  • UX Compare

    jezweb/claude-skills

    Compare UX patterns across multiple reference apps using pattern libraries produced by ux-extract.

    1.1k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Questions about Strategy Document

What does Strategy Document do?

Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses. Strategy Document is an agent skill from jezweb/claude-skills. Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses.

When should I use Strategy Document?

Strategy Document fits situations like: A business asks to articulate strategy; analyse competition; plan for growth; build a lean business plan.

How do I install Strategy Document in Claude Code?

Run `npx skills add jezweb/claude-skills --skill strategy-document -a claude-code`. Or copy the skill folder (plugins/writing/skills/strategy-document in jezweb/claude-skills) into .claude/skills/strategy-document in your project. Claude Code loads it when a task matches its description.

How do I install Strategy Document in Codex?

Run `npx skills add jezweb/claude-skills --skill strategy-document -a codex`. Or copy the skill folder (plugins/writing/skills/strategy-document in jezweb/claude-skills) into .agents/skills/strategy-document in your project. Codex loads it when a task matches its description.

Can I use Strategy Document in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jezweb/claude-skills --skill strategy-document -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/strategy-document, .gemini/skills/strategy-document, .github/skills/strategy-document and .opencode/skills/strategy-document in your project.

What does Strategy Document need to run?

SKILL.md names no scripts, command-line tools or credentials: Strategy Document is instructions for the agent only.

Does Strategy Document access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Strategy Document safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Strategy Document use?

Strategy Document is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Strategy Document use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Strategy Document?

Skills that share tags, products or a category with Strategy Document: Product Strategist (davila7/claude-code-templates, 32k stars), Space Chart HTML Plus (SpaceZephyr/design-buddy, 174 stars), Startup Metrics (guia-matthieu/clawfu-skills, 150 stars) and Partnerships Ecosystem (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Strategy Document?

jezweb (a GitHub user) maintains it in jezweb/claude-skills, which has 1,050 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 5, 2026.

Source: jezweb/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.