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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstrategy-documentExecute the skills CLI command in your project's root directory to begin installation:
Fetches strategy-document from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate strategy-document. Access via /strategy-document in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
697
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
697
stars
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
kagurananaga/official-document-writing-skill
travisjneuman/.claude
ityes22/game-design-document
Registry listing for strategy-document matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in strategy-document — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend strategy-document for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added strategy-document from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
strategy-document fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: strategy-document is focused, and the summary matches what you get after install.
Keeps context tight: strategy-document is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend strategy-document for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in strategy-document — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: strategy-document is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 71