Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

strategy-document战略文件

Agent Skill

strategy-document 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

10,290

周安装

442

GitHub Stars

750

下载量

3,607
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:strategy-document(战略文件)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/strategy-document
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill strategy-document
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill strategy-document

简介

strategy-document 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于基于关键词或任务场景的信息搜集与筛选需求。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态及是否涉及联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

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"

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.07%
按下载量换算1,301

Claude

28.07%
按下载量换算1,012

Cursor

16.61%
按下载量换算599

Gemini CLI

9.29%
按下载量换算335

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills