From strategy-memo
Structure business ideas into a 4-layer framework (Market/Value Proposition/Technology/Execution), check for logical gaps, and generate polished strategy memos
npx claudepluginhub dobachi/claude-skills-marketplace --plugin strategy-memoThis skill uses the workspace's default tool permissions.
> **Language:** Respond in the user's language. If unclear, default to the language of the user's message.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Language: Respond in the user's language. If unclear, default to the language of the user's message.
Transforms rough business ideas and insights into structured strategy memos using a 4-layer framework, with systematic gap analysis and logical consistency checking.
| Element | Description | Key Questions |
|---|---|---|
| Market Dynamics | Current state and trajectory | What is changing in this market? What are the macro/micro trends? |
| Customer Pain | Problems worth solving | Who suffers? How much does it cost them? How do they cope today? |
| Timing | Why this opportunity exists now | What has changed (technology, regulation, behavior) to create this window? |
| Competitive Landscape | Who else is here | Who are the incumbents? New entrants? What are their blind spots? |
| Element | Description | Key Questions |
|---|---|---|
| Core Offering | What we build/deliver | What is the product/service? What does it do concretely? |
| Differentiation | Why us over alternatives | What is our unique angle? What moat can we build? |
| Customer Value | Measurable impact | What ROI/outcome can customers expect? How do we prove it? |
| Positioning | Market perception | How do we want to be perceived? What category do we create or own? |
| Element | Description | Key Questions |
|---|---|---|
| Architecture | Technical approach | What is the high-level system design? Buy vs. build? |
| Key Technology Bets | Critical technical choices | What technologies are we betting on? What are the risks? |
| Data Strategy | Data as an asset | What data do we need? How do we acquire/generate/protect it? |
| Technical Moat | Defensibility through technology | What gets harder to replicate over time? Network effects? Data flywheel? |
| Element | Description | Key Questions |
|---|---|---|
| Team | Who executes | What capabilities do we need? What do we have vs. need to hire? |
| Milestones | Key checkpoints | What are the 3/6/12-month milestones? What proves/disproves the thesis? |
| Resources | Investment required | How much funding? What infrastructure? What partnerships? |
| Risks & Mitigations | What could go wrong | Top 3-5 risks and how we address each |
| Go-to-Market | How we launch and grow | First customers? Sales motion? Growth loops? |
Accept the user's raw input (idea memo, conversation notes, brainstorm output) and:
Generate a gap analysis table:
## Gap Analysis
| Layer | Element | Status | Notes |
|-------|---------|--------|-------|
| Market | Market Dynamics | Covered | Strong macro analysis |
| Market | Customer Pain | Partial | Pain identified but not quantified |
| Market | Timing | Gap | No "why now" argument |
| Market | Competitive Landscape | Covered | 3 competitors identified |
| Value Prop | Core Offering | Covered | Clear product description |
| Value Prop | Differentiation | Partial | Claimed but not evidenced |
| ... | ... | ... | ... |
Status levels:
Verify logical coherence across layers:
| Check | Description |
|---|---|
| Market-VP alignment | Does the value proposition address the identified market pain? |
| VP-Tech feasibility | Can the technology actually deliver the promised value? |
| Tech-Execution realism | Does the team/resource plan match the technical ambition? |
| Market-Execution timing | Do milestones align with market window? |
| Overall coherence | Does the story hold together end-to-end? |
# Strategy Memo: [Title]
**Date**: [Date]
**Author**: [Author]
**Status**: Draft / Review / Final
**Confidentiality**: [Level]
---
## Executive Summary
3-5 sentences capturing the core thesis, opportunity size, and recommended action.
## 1. Market Opportunity
### 1.1 Market Dynamics
### 1.2 Customer Pain Point
### 1.3 Why Now
### 1.4 Competitive Landscape
## 2. Value Proposition
### 2.1 Core Offering
### 2.2 Differentiation
### 2.3 Customer Value / ROI
### 2.4 Positioning
## 3. Technology & Product
### 3.1 Architecture Overview
### 3.2 Key Technology Bets
### 3.3 Data Strategy
### 3.4 Technical Moat
## 4. Execution Plan
### 4.1 Team & Capabilities
### 4.2 Milestones (3 / 6 / 12 months)
### 4.3 Resource Requirements
### 4.4 Risks & Mitigations
### 4.5 Go-to-Market Strategy
## 5. Open Questions
Numbered list of unresolved issues that need further investigation.
## 6. Next Steps
Concrete actions with owners and deadlines.
## Appendix
- Gap analysis table
- Assumptions log
- Sources
| Dimension | Strong | Adequate | Weak |
|---|---|---|---|
| Clarity | Thesis stated in one sentence | Thesis identifiable but verbose | Thesis unclear |
| Evidence | Data-backed claims with sources | Some data, some assertions | Mostly opinion |
| Completeness | All 4 layers substantively covered | Minor gaps acknowledged | Major layers missing |
| Coherence | Logical flow across all layers | Some disconnects noted | Contradictions present |
| Actionability | Clear next steps with owners/dates | General direction provided | No clear path forward |
| Mode | Description | When to Use |
|---|---|---|
| Expand | Deepen a specific layer or element | "Tell me more about the competitive landscape" |
| Challenge | Stress-test assumptions and claims | "What could go wrong with this thesis?" |
| Sharpen | Tighten the argument, remove fluff | "Make this more concise and compelling" |
| Pivot | Explore alternative framings | "What if we targeted a different segment?" |