brainstorm
Skill33 starsChanged 6 months agoMITView on GitHub
Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.
We split this skill into the rules it gives an agent
11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read brand/ files if they exist (voice-profile.md, audience.md, positioning.md, learnings.md).
- Very specific: line 31
If skipping: "Your request is specific enough to execute directly.
- Distinctive: line 35
Ask ONE question at a time.
- Distinctive: line 46
Stop as soon as you have enough to propose approaches.
- Distinctive: line 64
Ask the user to pick one, combine elements, or explore further.
- Very specific: line 78
Write a structured brief to marketing/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md:
- Distinctive: line 122
After writing the brief:
- Distinctive: line 126
Do not list all 50 skills.
- Distinctive: line 146
Follow the output formatting rules from /cmo rules/output-format.md.
- Very specific: line 167
If the user has no audience data, start with audience-research, not guessing
- Distinctive: line 168
Don't brainstorm pricing, launches, or SEO strategy — those have dedicated skills
“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/brainstorm — Marketing Brainstorm
Structured exploration when marketing direction is unclear. You produce a brief that tells /cmo where to route next.
For brand memory protocol, see /cmo rules/brand-memory.md.
On Activation
- Read
brand/files if they exist (voice-profile.md, audience.md, positioning.md, learnings.md). They enhance but never gate. - Assess the user's request clarity level.
Phase 0: Assess Clarity
Gate check. If the request is already specific, skip brainstorming:
| Signal | Action |
| "Write a landing page for X" | Skip. Route to direct-response-copy. |
| "Do SEO for my blog" | Skip. Route to keyword-research. |
| "I want to market my app" | Proceed. Multiple valid paths. |
| "What should I do next?" | Proceed. No clear direction. |
| "Help me think through our launch" | Proceed. Needs exploration. |
If skipping: "Your request is specific enough to execute directly. Routing to /<skill> instead of brainstorming."
Phase 1: Understand the Challenge
Ask ONE question at a time. Prefer multiple choice when natural options exist. Skip questions already answered by brand/ context.
Questions to cover (in order, stop when clear):
- Goal — What are you trying to achieve? (awareness / leads / revenue / retention / launch)
- Product — What are you marketing? (Brief description if not obvious from project context)
- Audience — Who buys this? (Skip if
brand/audience.mdexists and is current — confirm briefly instead: "Your audience profile says X. Still accurate?") - Channels — Where does your audience hang out? (search / social / email / communities / paid)
- Constraints — Budget, timeline, team size, tools available?
- Competition — Who else does this? What makes you different? (Skip if
brand/competitors.mdexists — reference it instead)
Stop as soon as you have enough to propose approaches. 3-4 questions is usually enough.
Phase 2: Explore Approaches
Present 2-3 concrete strategic directions. For each:
### Approach [N]: [Name]
**Core angle:** [One sentence positioning]
**Channels:** [Primary → Secondary]
**Audience fit:** [Why this resonates with the target]
**Timeline:** [Quick win vs. long play]
**Pros:** [2-3 bullet points]
**Cons:** [1-2 bullet points]
**Best when:** [Conditions that make this the right choice]Ask the user to pick one, combine elements, or explore further.
Handling responses:
| User says | Action |
| Picks an approach | Move to Phase 3 with that approach |
| Wants to combine | Merge the relevant elements into a hybrid approach, confirm the blend, then move to Phase 3 |
| Rejects all approaches | Ask what felt wrong. Probe for the constraint or preference you missed. Generate 1-2 new approaches informed by their feedback |
| "I want to do all of them" | Recommend a sequence: "Start with [approach] because [reason]. If that works, layer in [approach 2] in week 3." Prioritize, don't parallelize |
| Wants to explore further | Ask one targeted follow-up question, then generate 1-2 additional approaches |
Phase 3: Capture Marketing Brief
Write a structured brief to marketing/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md:
---
type: marketing-brainstorm
date: YYYY-MM-DD
topic: [kebab-case topic]
goal: [awareness|leads|revenue|retention|launch]
chosen-approach: [N]
---
# Marketing Brief: [Topic]
## Context
[What we're marketing and why now]
## Chosen Approach
[Selected direction with rationale]
## Target Audience
[Who we're reaching]
## Channels
[Primary and secondary channels]
## Key Messages
[3-5 core messages]
## Constraints
[Budget, timeline, tools]
## Success Metrics
[How we'll measure impact]
## Structured Handoff
next-skill: [skill-name]
confidence: [high|medium|low]
context-summary: "[One line summary for /cmo routing]"The next-skill field is critical — it tells /cmo where to route after brainstorming.
Phase 4: Route Back to /cmo
After writing the brief:
"The brainstorm is complete. Brief saved to marketing/brainstorms/[filename]. Run /cmo to execute the next step (/[next-skill]), or invoke /<next-skill> directly."
Do not list all 50 skills. Recommend the ONE next skill based on the brief.
Worked Example
User request: 'I just built a verified meal delivery app, what should I do for marketing?'
Approach 1: Community-Led Growth Build presence in health-focused community spaces (neighborhood Slack groups, campus food subreddits, verified-source food Instagram). Create shareable content that spreads through existing trust networks. → next-skill: audience-research
Approach 2: SEO + Content Capture 'verified meal delivery' search traffic with city-specific landing pages. Write comparison content ('Is DoorDash organic?') to redirect competitor traffic. → next-skill: keyword-research
Recommended: Approach 1 — community trust is the moat for verification-driven products. SEO is Phase 2 after you have testimonials to feature.
Output Format
Follow the output formatting rules from /cmo rules/output-format.md. Key requirements:
- Header with "MARKETING BRAINSTORM" and date
- Each approach as a clearly separated section
- FILES SAVED section showing the brief path
- WHAT'S NEXT section with the recommended next-skill
Anti-Patterns
| Anti-pattern | Instead | Why |
| Asking 5+ questions at once | One question at a time, multiple choice | Builders get overwhelmed by question walls. Each answer should shape the next question. |
| Jumping straight to tactics | Explore the strategic direction first | Tactics without strategy leads to scattered effort. "Post on TikTok" isn't a plan. |
| Proposing 5+ approaches | 2-3 focused options, not a menu | More options = more decision paralysis. The builder came here because they were stuck — don't make it worse. |
| Generic advice ("build an audience") | Specific to their product and context | Anyone can say "build an audience." The value is knowing WHICH audience, WHERE, with WHAT message. |
| Brainstorming when direction is clear | Skip to the execution skill | Brainstorming is exploration, not procrastination. If they know what they want, execute. |
| Leaving the user without a next step | Always include next-skill in the brief | A brainstorm that doesn't lead to action is just a meeting. The handoff is the whole point. |
YAGNI Principles
- Resist adding channels you can't actually execute on
- One campaign well-executed beats three half-started
- If the user has no audience data, start with
audience-research, not guessing - Don't brainstorm pricing, launches, or SEO strategy — those have dedicated skills
- The brief is a compass, not a bible. It should fit on one page.
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- jtydhr88/ComfyTV★ 1.2ksame name
- event-driven-io/emmett★ 558same name
- ZaxbyHub/opencode-swarm★ 517same name
- zaxbysauce/opencode-swarm★ 517same name
- automagik-dev/genie★ 345same name
- namastexlabs/automagik-genie★ 345same name
- bkywksj/knowledge-base★ 337same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
179 more not listed
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.
Used alongsideProjects with it also use playtest-report, team-polish and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 9 projects that use this
CoralGameSkillteam-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 11 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 6 projects that use this
- +9 more from CoralGame
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- studio/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- studio/CLAUDE.mdCLAUDE.md
- agent-email-inboxSkill
- ai-seoSkill
- app-store-screenshotsSkill
- audience-researchSkill
- axiSkill
- brand-kit-playgroundSkill
- brand-voiceSkill
- build-with-exaSkill
- churn-preventionSkill
- cmo-remotionSkill
- cmoSkill
- company-researchSkill
- competitive-intelSkill
- competitor-alternativesSkill
- content-atomizerSkill
- conversion-flow-croSkill
- create-skillSkill
- creativeSkill
- deepen-planSkill
- direct-response-copySkill
- document-reviewSkill
- email-sequencesSkill
- exa-contentsSkill
- exa-searchSkill
- firecrawlSkill
- free-tool-strategySkill
- frontend-slidesSkill
- higgsfield-generateSkill
- higgsfield-product-photoshootSkill
- higgsfield-soul-idSkill
- image-genSkill
- keyword-researchSkill
- landscape-scanSkill
- launch-strategySkill
- lead-generationSkill
- lead-magnetSkill
- manimce-best-practicesSkill
- manim-composerSkill
- manimgl-best-practicesSkill
- marketing-demoSkill
- marketing-psychologySkill
- mktg-setupSkill
- mktg-xSkill
- newsletterSkill
- off-page-seoSkill
- openseo-coachSkill
- openseo-competitive-landscapeSkill
- openseo-competitor-analysisSkill
- openseo-keyword-clusteringSkill
- openseo-keyword-researchSkill
- openseo-link-prospectingSkill
- openseo-project-setupSkill
- openseoSkill
- page-croSkill
- paper-marketingSkill
- positioning-anglesSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

