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.
Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses.
$ npx skills add jezweb/claude-skills --skill strategy-document -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jezweb/claude-skills strategy-document --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .claude/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-documentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jezweb/claude-skills --skill strategy-document -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jezweb/claude-skills strategy-document --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/writing/skills/strategy-document .agents/skills/strategy-document && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .agents/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill strategy-document -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jezweb/claude-skills strategy-document --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/writing/skills/strategy-document .cursor/skills/strategy-document && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .cursor/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jezweb/claude-skills.git --path plugins/writing/skills/strategy-document--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jezweb/claude-skills --skill strategy-document -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jezweb/claude-skills strategy-document --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/writing/skills/strategy-document .gemini/skills/strategy-document && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .gemini/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jezweb/claude-skills strategy-documentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jezweb/claude-skills --skill strategy-document -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/writing/skills/strategy-document .github/skills/strategy-document && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .github/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill strategy-document -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jezweb/claude-skills strategy-document --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/writing/skills/strategy-document .opencode/skills/strategy-document && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "strategy-document" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/strategy-document into .opencode/skills/strategy-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "strategy-document", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
strategy-documentWrite 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. 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.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 64965d9. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from jezweb/claude-skills at commit 64965d9, republished under its MIT licence (© jezweb). 1,536 words, ~2,964 tokens.
.claude/skills/strategy-document/SKILL.md (or your agent's skills folder).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.
Ask the user which document type they need:
If the user is unsure, ask what decision they are trying to make. That usually reveals the right mode:
Ask for:
The audience determines the level of detail. A bank wants financial projections. A founder wants clarity. A team wants direction.
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.
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.
| 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.
After the grid, add a section that translates findings into actions:
Strategic implications:
This is the most valuable part of a SWOT. The grid without implications is an exercise in categorisation, not strategy.
Use when the audience is the founder or a small team needing clarity. One paragraph per section, no padding.
| Section | What to write |
|---|---|
| Problem | What pain exists? Who feels it? How do they cope today? |
| Solution | What does the business offer? In one sentence. |
| Key Metrics | 3-5 numbers that indicate health (MRR, churn, CAC, LTV, NPS) |
| Unique Value Prop | Why this business over alternatives? One sentence. |
| Channels | How do customers find you? Rank by effectiveness. |
| Revenue Streams | How does money come in? List each stream with approximate % of total. |
| Cost Structure | Top 5 cost categories with approximate monthly/annual figures. |
| Unfair Advantage | What 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.
Adds to the lean format:
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.
| Too vague | Specific |
|---|---|
| "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" |
| 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.
At quarter end, score each KR from 0.0 to 1.0:
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.
Start with a comparison matrix, then interpret it.
Comparison matrix:
| Factor | Your Business | Competitor A | Competitor B | Competitor C |
|---|---|---|---|---|
| Price point | $X/mo | $Y/mo | $Z/mo | Free tier + $W/mo |
| Key feature 1 | Yes | Yes | No | Partial |
| Key feature 2 | No | Yes | Yes | Yes |
| Target market | AU SMEs | Enterprise | Startups | All segments |
| Strength | Personal service | Scale | Price | Brand recognition |
| Weakness | Small team | Impersonal | Limited features | Slow support |
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.
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.
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.
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
Just SKILL.md in plugins/writing/skills/strategy-document of jezweb/claude-skills.
Open the folder on GitHubat commit 64965d9
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Strategy Document this skilljezweb/claude-skills | 1.1k | — | ~3k | Automated safety check: Pass | MIT | |
| Product Strategistdavila7/claude-code-templates | 32k | 3 repos | ~248 | Automated safety check: Pass | MIT | |
| Space Chart HTML PlusSpaceZephyr/design-buddy | 174 | — | ~1.6k | Automated safety check: Pass | None | |
| Startup Metricsguia-matthieu/clawfu-skills | 150 | — | ~5k | Automated safety check: Pass | MIT | |
| Partnerships EcosystemLeoYeAI/openclaw-master-skills | 2.2k | — | ~5k | Automated safety check: Pass | MIT | |
| Strategic Planningw95/awesome-claude-corporate-skills | 235 | — | ~2.2k | Automated safety check: Pass | MIT |
davila7/claude-code-templates
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling.
SpaceZephyr/design-buddy
AI 全能图表生成器(扩展版)。一键生成 35+ 种设计美观的图表 HTML 文件,涵盖技术架构、流程逻辑、业务战略、数据可视化、信息展示 5 大类别。支持 3 种内置视觉风格(黑白简约、深色暗调、Claude 暖色)+ 品牌风格扩展。
guia-matthieu/clawfu-skills
Know the metrics that matter at each stage and what investors actually look for.
LeoYeAI/openclaw-master-skills
World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills.
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…
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.
jezweb/claude-skills
Build conversational AI voice agents on the ElevenLabs platform.
jezweb/claude-skills
Generate custom favicons from logos, text, or brand colours.
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
Test website responsiveness across viewport widths using browser automation.
jezweb/claude-skills
Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
Compare UX patterns across multiple reference apps using pattern libraries produced by ux-extract.
Categories
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.
Strategy Document fits situations like: A business asks to articulate strategy; analyse competition; plan for growth; build a lean business plan.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Strategy Document is instructions for the agent only.
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.
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.
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.
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.
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.
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.