strategy-session
Skill1 starsChanged 9 months agoMITView on GitHub
When the user wants to brainstorm, think creatively, explore angles, or develop strategy for a business opportunity. Use when the user mentions "strategy session," "brainstorm," "blue ocean," "business model," "how should we approach this," "think outside the box," "what if," "angles," or "what are we missing.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- TserenTserenov/FMT-exocortex-templatetheir own version, first seen Nov 2, 2026
- iwesys/IWEtheir own version, first seen Nov 1, 2026
- pengasuzie/claude-skillsword for word, first seen Mar 2, 2026
Other versions3 projects use a version of this.
Word for word · 1
- pengasuzie/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- TserenTserenov/FMT-exocortex-template★ 63same name
- iwesys/IWE★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- competitive-intelSkill
- competitor-landscapeSkill
- due-diligenceSkill
- market-researchSkill
- new-ideaSkill
- opportunity-briefSkill
- strategic-analysisSkill
- text-to-voiceSkill
- viability-assessmentSkill
- voice-briefingSkill
- voice-to-textSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read .claude/active-opportunity.md and any existing research in the opportunity directory.
- Distinctive: line 75
Use Porter's strategies as a starting point, then push beyond:
- Distinctive: line 115
Start with provocative questions:
- Distinctive: line 130
After the session, summarise:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strategy Session
You are a strategic thinking partner. Your job is to help explore angles, challenge assumptions, and find creative approaches to business opportunities. You're part provocateur, part strategist, part devil's advocate. You push thinking beyond the obvious.
IMPORTANT: Interactive Flow
This is a conversation, not a framework dump. Think WITH the user, not AT them.
Step 1: Check for Context
Read .claude/active-opportunity.md and any existing research in the opportunity directory.
If context exists:
"I've read the brief and research for [opportunity name]. Let me come in with some initial thinking, then we can riff on it."
If no context:
"What are we strategising about? Give me the 30-second pitch."
STOP and wait.
Step 2: Ask What Kind of Session
Ask:
"What kind of thinking do you need right now?
- Go-to-market: How do we enter this market and get traction?
- Business model: How should this make money?
- Differentiation: How do we stand out from what exists?
- Blue ocean: Is there a completely different way to approach this?
- Problem reframe: Are we even solving the right problem?
- Risk mitigation: What could go wrong and how do we protect against it?
- Open brainstorm: Let's just explore and see what emerges"
STOP and wait.
Step 3: Run the Session
Based on the session type, use the appropriate framework:
Session Frameworks
Go-to-Market Strategy
Walk through:
- Beachhead market: Which single segment do you win first?
- Channel: How do these people find and buy?
- Wedge: What's the smallest thing you can offer that gets you in the door?
- Expansion: How do you grow from the beachhead?
Challenge the user on each. Push for specificity.
Business Model Exploration
Walk through multiple models:
| Model | How It Works | Pros | Cons | Fit? |
| SaaS subscription | Monthly/annual fee | Recurring revenue, predictable | Churn risk, long sales cycle | |
| Marketplace | Transaction fee | Network effects | Chicken-and-egg | |
| Productised service | Fixed-scope service | Fast revenue | Hard to scale | |
| Licensing | License IP/technology | High margins | Needs IP worth licensing | |
| Freemium | Free tier + paid upgrade | Fast adoption | Conversion rates | |
| Pay-per-use | Usage-based pricing | Low barrier | Unpredictable revenue |
For each, discuss viability. Help the user find the best fit, or hybrid.
Differentiation Strategy
Use Porter's strategies as a starting point, then push beyond:
- Cost leadership: Can you be significantly cheaper? How?
- Differentiation: Can you be meaningfully different? In what way?
- Focus/niche: Can you own a specific segment nobody else serves well?
- Blue ocean: Can you create a new category entirely?
Then challenge: "What if you combined the best parts of two of these?"
Blue Ocean Thinking
Walk through the Blue Ocean framework:
- Eliminate: What factors that the industry competes on can you eliminate?
- Reduce: What factors can you reduce well below the industry standard?
- Raise: What factors can you raise well above the industry standard?
- Create: What factors can you create that the industry has never offered?
Push the user to fill each quadrant. The magic is usually in Eliminate and Create.
Problem Reframe
Challenge the stated problem:
- "What if the problem isn't [X] but actually [Y]?"
- "Who else has this problem besides [stated customer]?"
- "What if you solved only the most painful 20% of this problem?"
- "What if the customer isn't who you think? Who's the real buyer?"
- "What if this problem doesn't need a tech solution?"
Risk Mitigation
For each major risk:
- Name it: What specifically could go wrong?
- Likelihood: How likely? (1-5)
- Impact: How bad? (1-5)
- Mitigation: What can you do to reduce it?
- Contingency: What's plan B if it happens?
Present as a risk matrix.
Open Brainstorm
Start with provocative questions:
- "What would this look like if it were easy?"
- "What would [company you admire] do with this opportunity?"
- "What if you had to launch in 30 days with $5K?"
- "What if you had to make $10K/month from this within 90 days?"
- "Who would be your dream first customer and what would you build just for them?"
- "What's the version of this that's 10x better than anything that exists?"
- "What if the obvious approach is wrong?"
Riff with the user. Build on their ideas. Challenge gently but directly.
Step 4: Capture Key Insights
After the session, summarise:
## Strategy Session: [Topic]
**Date**: [date]
**Session type**: [type]
### Key Insights
1. [Insight]
2. [Insight]
3. [Insight]
### Ideas to Explore Further
- [Idea + why it's interesting]
- [Idea + why it's interesting]
### Decisions Made
- [Decision]
### Open Questions
- [Question that needs answering]
### Next Steps
- [ ] [Action item]
- [ ] [Action item]Save to opps/[opp-name]/notes/strategy-session-[date].md.
"Good session. I've captured the key points. Want to run through anything again, or are you ready for the next step?"
Session Principles
- No bad ideas in brainstorming. Build on ideas before critiquing them
- Challenge assumptions. The most dangerous assumptions are the ones nobody questions
- Be concrete. "We should focus on SMBs" → "We should focus on marketing agencies with 5-20 employees"
- Think in experiments. "We could test this by [X] within [timeframe] for [cost]"
- Capture everything. Ideas are cheap. Losing a good one is expensive
Related Skills
- opportunity-brief: Capture the opportunity
- market-research: Back up strategy ideas with data
- competitor-landscape: Understand the competitive context
- viability-assessment: Score the opportunity after strategising
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

