# Strategy Plan Writing

> Write business strategy, operations planning, market analysis, and 运营策划案 documents — multi-dimensional analysis, data-supported, actionable plans for non-software business domains.

- Skill: `jorinyang/strategy-plan-writing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jorinyang/strategy-plan-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jorinyang/strategy-plan-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jorinyang (https://skillmd.com/u/jorinyang)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/jorinyang/strategy-plan-writing

---


# Strategy & Operations Plan Writing

Write high-quality strategy documents, operations plans (运营策划案), market analysis reports, and business proposals. Covers non-software business domains: tourism/wenlv, retail, services, product launches, marketing campaigns, etc.

## Triggers

### 通用领域触发矩阵

战略/运营策划案覆盖7大领域，25个子场景。

| 领域 | 场景 | 触发信号 | 示例 |
|------|------|---------|------|
| **技术/SaaS** | 技术产品GtM | 用户需要技术产品上市策略 | "策划这个SaaS工具的go-to-market方案" |
| 技术/SaaS | 开发者生态 | 用户需要开发者社区策略 | "做一个开发者关系运营方案" |
| 技术/SaaS | 技术商业化 | 用户需要技术变现策略 | "策划这个开源项目的商业化方案" |
| 技术/SaaS | 云市场策略 | 用户需要云服务市场方案 | "做一个云服务区域拓展的运营方案" |
| **文旅/体验** | 景区运营 | 用户需要景区/基地运营方案 | "策划一个户外体验基地的全年运营" |
| 文旅/体验 | 线路产品 | 用户需要文旅线路策划 | "设计一条深度体验线路的产品方案" |
| 文旅/体验 | 节庆活动 | 用户需要文旅活动策划 | "做一个暑期水上活动的运营策划案" |
| 文旅/体验 | 研学产品 | 用户需要研学产品设计 | "策划一个青少年户外研学产品" |
| **零售/消费** | 新品上市 | 用户需要新品上市策略 | "策划这个消费品的新品上市方案" |
| 零售/消费 | 渠道拓展 | 用户需要渠道拓展策略 | "做一个线下渠道拓展的运营方案" |
| 零售/消费 | 私域运营 | 用户需要私域运营策略 | "策划一个私域会员运营方案" |
| **服务/咨询** | 服务产品化 | 用户需要服务产品化方案 | "策划咨询服务从定制到产品的转型" |
| 服务/咨询 | 客户增长 | 用户需要服务类获客策略 | "做一个专业服务的客户增长方案" |
| 服务/咨询 | 定价/包装 | 用户需要服务定价方案 | "策划这个培训服务的定价和包装" |
| **教育/培训** | 课程运营 | 用户需要课程运营方案 | "策划一个AI课程的推广运营方案" |
| 教育/培训 | 培训体系 | 用户需要培训体系设计 | "做一个企业内训的体系化方案" |
| 教育/培训 | 知识付费 | 用户需要知识付费策略 | "策划一个知识付费产品的运营方案" |
| **内容/媒体** | 账号运营 | 用户需要自媒体运营策略 | "策划这个IP账号的运营方案" |
| 内容/媒体 | 内容矩阵 | 用户需要多平台内容策略 | "做一个多平台内容矩阵运营方案" |
| 内容/媒体 | IP孵化 | 用户需要IP孵化策略 | "策划一个个人IP的孵化方案" |
| **企业服务** | B2B市场 | 用户需要B2B市场策略 | "做一个B2B SaaS的市场拓展方案" |
| 企业服务 | 客户成功 | 用户需要客户成功体系 | "策划客户成功团队的运营方案" |
| 企业服务 | 合作伙伴 | 用户需要合作伙伴计划 | "做一个渠道合作伙伴招募运营方案" |
| 企业服务 | 企业品牌 | 用户需要企业品牌策略 | "做一个企业品牌建设的运营方案" |
| 企业服务 | 内部运营 | 用户需要内部运营优化 | "策划一个跨部门协作效率提升方案" |

### 手动触发

Use this skill when the user asks for:
- 运营策划案 / 运营方案 / 营销策划案 / 策略方案
- Business strategy document / business plan / GtM plan
- 全链路分析 (full-chain analysis)
- Market entry strategy / competitive analysis / channel strategy
- Multi-dimensional business analysis across operational dimensions
- Any document that requires: data support, framework design, financial modeling, execution roadmap

## Quality Standards (User's Explicit Requirements)

The user has articulated specific quality standards for this class of work. These are NON-NEGOTIABLE:

1. **第一性原则 (First Principles)**: Ground analysis in root causes and fundamental truths, not surface trends. Question every assumption. The core question: "What is the user/customer actually buying, and why?"

2. **可实践性 (Actionable)**: Every recommendation must include specific "how" — tools, team size, timelines, budget ranges, SOPs. No vague "consider doing X." If you recommend "AI content production," specify which tools, what workflow, expected output per day.

3. **严谨 (Rigorous)**: Logical chain must hold. Every strategy recommendation must trace back to a diagnosed pain point or opportunity from the source materials. No unsupported claims.

4. **务实 (Practical)**: Recommendations must fit the user's actual resource constraints (budget, team size, timeline). If they have a 3-person team, don't propose a 20-person organizational structure. If they have zero ad budget, don't lead with paid acquisition.

5. **有数据支持 (Data-Supported)**: Use industry benchmarks, conversion rate data, pricing references, market size figures. When exact data isn't available, use reasonable estimates clearly marked as "约" (approximately) or "参考" (reference). Never fabricate precise numbers.

6. **能拿到结果 (Results-Oriented)**: Every chapter should have measurable outcomes. Include KPI dashboards, milestone checkpoints, and success/failure criteria.

## Two-Tier Delivery Pattern (Cold-Start / Complex Launches)

When the user asks for both strategy AND execution in one request (typical for cold-start / new product launch / online matrix planning), split into TWO documents, not one:

**v1 — Strategy Plan (策略层):**
- Market anchors & industry data
- First-principles analysis
- Core decisions (account strategy, platform selection, team, budget)
- 90-day roadmap at the milestone level
- KPI dashboard

**v2 — Execution Plan (执行层):**
- Per-platform account setup specs (names, bios, menu structures, POI)
- Content type breakdown with script templates
- 30-day editorial calendar (day-by-day)
- Publishing SOPs and best-time schedules
- Paid promotion strategy (DOU+, 薯条) with phased budgets
- Comment/interaction scripts and conversion funnels
- Cross-platform coordination workflow (一鱼多吃)
- Day 1-7 launch checklist

**Why split:** A single document that covers both strategy and per-platform execution detail becomes unreadable (>20K words) and neither layer gets done well. The strategy document is for decision-makers; the execution document is for operators. Two audiences, two docs.

**Naming convention:** `{主题}_策划案_v1.md` + `{主题}_各平台执行方案_v1.md`

## Document Structure Pattern

For multi-dimensional business analysis, use this proven structure:

```
1. Market Overview & Data Anchors (宏观数据锚点)
2-12. Full-chain dimension-by-dimension analysis
13. Execution Roadmap + KPIs + Budget
```

Each dimension chapter should contain:
- **Diagnosis**: What's the current state / problem from source materials
- **Strategy**: What to do about it
- **Tactics**: Specific actions, tools, workflows
- **Metrics**: How to measure success
- **Pitfalls**: What could go wrong and how to mitigate

## Research Workflow

When the user provides source materials (meeting notes, transcripts):

1. **Deep-read all attachments first** — Extract all strategic decisions, pain points, constraints, and data points. These are your primary source.

2. **Attempt web research for supporting data** — Market size, industry benchmarks, competitor examples, case studies. Use browser search or terminal curl. BUT: in WSL environments, Bing China often returns garbage results for Chinese business queries, and Google/DuckDuckGo may timeout behind proxies.

3. **Pivot to training knowledge when search fails** — If 2-3 search attempts yield nothing useful, STOP searching. Your training data contains substantial industry knowledge. Clearly mark training-knowledge data as "约" or "参考" rather than cited sources. The quality of your domain knowledge + the user's source materials is sufficient for a high-quality plan.

4. **Never spend >5 minutes on research dead ends** — If searches are not productive, pivot immediately to writing. The user's deadline matters more than perfect citations.

## Deliverable Format

- **Simple requests:** single comprehensive markdown file
- **Cold-start / complex launches:** two-tier (strategy v1 + execution v2), see Two-Tier Delivery Pattern
- Use tables for data-heavy sections (market data, pricing models, team configs, KPI dashboards)
- Include an executive-level table of contents
- Save to the workspace directory with clear naming: `{主题}_策划案_v{版本号}.md`

## Linked Resources

- `references/china-research-pitfalls.md` — WSL search workarounds for China-market business research
- `references/execution-plan-template.md` — Per-platform execution plan structure template (v2 tier)
- `templates/strategy-plan-template.md` — Starter template for strategy/operations plan documents

## Common Pitfalls

1. **Over-relying on search for data validation** — In Chinese business contexts, web search often fails due to proxy/network issues. Trust your training knowledge when searches fail. Mark estimates honestly.

2. **Making the plan too abstract** — "Build a brand" is useless advice. "Post 3 Douyin videos/day targeting 25-35yo parents, measure CTR after 30 days, aim for >3% engagement rate" is actionable.

3. **Ignoring resource constraints** — Always ask: "Can they actually do this with their current team/budget?" If not, phase it.

4. **Forgetting the "first principles" test** — After writing each section, ask: "Would this still be true if all the industry jargon were stripped away?"

5. **Over-structuring** — Not every section needs sub-sections. If a dimension only needs 2 paragraphs and a table, that's fine. Don't inflate to fill space.

6. **Over-cramming strategy + execution into one document** — When the user needs both strategic decisions (账号策略, platform selection, budget) AND per-platform execution detail (script templates, 30-day calendars, SOPs), a single doc becomes bloated and unreadable (>20K words). Split into v1 (strategy, for decision-makers) and v2 (execution, for operators).