菜单
Analyze strategic positioning and explore future scenarios. Use when user wants "SWOT analysis", "competitive forces", "scenario planning", "what if", "strategic assessment", "market forces", "porter's", or needs to evaluate strategic options and potential futures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | strategic-analysis |
| description | Analyze strategic positioning and explore future scenarios. Use when user wants "SWOT analysis", "competitive forces", "scenario planning", "what if", "strategic assessment", "market forces", "porter's", or needs to evaluate strategic options and potential futures. |
| allowed-tools | Read |
Assess strategic positioning, competitive dynamics, and explore alternative futures. Move from gut feeling to structured strategic thinking.
| Need | Use | Why |
|---|---|---|
| Assess current strategic position | SWOT Analysis | Balanced view of internal/external factors |
| Understand competitive dynamics | Porter's Five Forces | Maps industry pressure points |
| Explore possible futures | Scenario Planning | Prepares for multiple outcomes |
| Test assumptions quickly | What-If Analysis | Rapid exploration of variables |
Default: Use SWOT for current state assessment, Scenario Planning for future uncertainty.
Structured assessment of Strengths, Weaknesses, Opportunities, and Threats. Internal vs external, positive vs negative.
Read cookbook/swot.md
Analyze competitive intensity through five structural forces: rivalry, suppliers, buyers, substitutes, new entrants.
Read cookbook/porters-five-forces.md
Develop multiple plausible futures and strategies that work across them. Prepare for uncertainty.
Read cookbook/scenario-planning.md
Rapidly explore how changes to key variables would affect outcomes. Test sensitivity and assumptions.
Read cookbook/what-if-analysis.md
Challenge and stress-test ideas through adversarial thinking. Use when user wants to "poke holes", "challenge this", "what could go wrong", "devil's advocate", "stress test", "red team", "pre-mortem", "review this", "validate", "audit", or needs to find weaknesses before they become problems. (project)
Go style and best practices guide synthesized from Google, Uber, and official Go documentation. This skill should be used when writing, reviewing, or refactoring Go code. Triggers on tasks involving Go packages, error handling, concurrency, interfaces, or performance optimization.
Generate creative ideas through structured brainstorming techniques. Use when user wants to "brainstorm", "generate ideas", "think creatively", "SCAMPER", "walt disney method", "reverse brainstorm", "come up with options", or needs to break out of conventional thinking.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Explore problems from multiple perspectives through structured role-playing techniques. Use when user wants to "see different viewpoints", "consider perspectives", "what would X think", "six hats", "stakeholder view", "persona analysis", or needs to understand how different people would approach a problem.
Dig to fundamental truths and real causes behind problems. Use when user asks "why does this happen", "what's the real problem", "root cause", "first principles", "jobs to be done", "JTBD", "five whys", "fundamental reason", or needs to understand underlying causes rather than symptoms.
