brainstorm

Name: brainstorm
Author: MoizIbnYousaf

27stars5forks

How to install brainstorm?

moizibnyousaf/marketing-cli/brainstorm

$npx -y skills add MoizIbnYousaf/marketing-cli --skill brainstorm

Installs into the current project.

Summary

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 app

Files · 1

View on GitHub

SKILL.md

1	# /brainstorm — Marketing Brainstorm
2
3	Structured exploration when marketing direction is unclear. You produce a brief that tells /cmo where to route next.
4
5	For brand memory protocol, see /cmo [rules/brand-memory.md](../cmo/rules/brand-memory.md).
6
7	## On Activation
8
9	1. Read `brand/` files if they exist (voice-profile.md, audience.md, positioning.md, learnings.md). They enhance but never gate.
10	2. Assess the user's request clarity level.
11
12	## Phase 0: Assess Clarity
13
14	Gate check. If the request is already specific, skip brainstorming:
15
16	\| Signal \| Action \|
17	\|--------\|--------\|
18	\| "Write a landing page for X" \| Skip. Route to `direct-response-copy`. \|
19	\| "Do SEO for my blog" \| Skip. Route to `keyword-research`. \|
20	\| "I want to market my app" \| Proceed. Multiple valid paths. \|
21	\| "What should I do next?" \| Proceed. No clear direction. \|
22	\| "Help me think through our launch" \| Proceed. Needs exploration. \|
23
24	If skipping: "Your request is specific enough to execute directly. Routing to `/<skill>` instead of brainstorming."
25
26	## Phase 1: Understand the Challenge
27
28	Ask ONE question at a time. Prefer multiple choice when natural options exist. Skip questions already answered by brand/ context.
29
30	Questions to cover (in order, stop when clear):
31
32	1. Goal — What are you trying to achieve? (awareness / leads / revenue / retention / launch)
33	2. Product — What are you marketing? (Brief description if not obvious from project context)
34	3. Audience — Who buys this? (Skip if `brand/audience.md` exists and is current — confirm briefly instead: "Your audience profile says X. Still accurate?")
35	4. Channels — Where does your audience hang out? (search / social / email / communities / paid)
36	5. Constraints — Budget, timeline, team size, tools available?
37	6. Competition — Who else does this? What makes you different? (Skip if `brand/competitors.md` exists — reference it instead)
38
39	Stop as soon as you have enough to propose approaches. 3-4 questions is usually enough.
40
41	## Phase 2: Explore Approaches
42
43	Present 2-3 concrete strategic directions. For each:
44
45	```
46	### Approach [N]: [Name]
47
48	Core angle: [One sentence positioning]
49	Channels: [Primary → Secondary]
50	Audience fit: [Why this resonates with the target]
51	Timeline: [Quick win vs. long play]
52	Pros: [2-3 bullet points]
53	Cons: [1-2 bullet points]
54	Best when: [Conditions that make this the right choice]
55	```
56
57	Ask the user to pick one, combine elements, or explore further.
58
59	Handling responses:
60
61	\| User says \| Action \|
62	\|-----------\|--------\|
63	\| Picks an approach \| Move to Phase 3 with that approach \|
64	\| Wants to combine \| Merge the relevant elements into a hybrid approach, confirm the blend, then move to Phase 3 \|
65	\| Rejects all approaches \| Ask what felt wrong. Probe for the constraint or preference you missed. Generate 1-2 new approaches informed by their feedback \|
66	\| "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 \|
67	\| Wants to explore further \| Ask one targeted follow-up question, then generate 1-2 additional approaches \|
68
69	## Phase 3: Capture Marketing Brief
70
71	Write a structured brief to `marketing/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`:
72
73	```markdown
74	---
75	type: marketing-brainstorm
76	date: YYYY-MM-DD
77	topic: [kebab-case topic]
78	goal: [awareness\|leads\|revenue\|retention\|launch]
79	chosen-approach: [N]
80	---
81
82	# Marketing Brief: [Topic]
83
84	## Context
85	[What we're marketing and why now]
86
87	## Chosen Approach
88	[Selected direction with rationale]
89
90	## Target Audience
91	[Who we're reaching]
92
93	## Channels
94	[Primary and secondary channels]
95
96	## Key Messages
97	[3-5 core messages]
98
99	## Constraints
100	[Budget, timeline, tools]
101
102	## Success Metrics
103	[How we'll measure impact]
104
105	## Structured Handoff
106	next-skill: [skill-name]
107	confidence: [high\|medium\|low]
108	context-summary: "[One line summary for /cmo routing]"
109	```
110
111	The `next-skill` field is critical — it tells /cmo where to route after brainstorming.
112
113	## Phase 4: Route Back to /cmo
114
115	After writing the brief:
116
117	"The brainstorm is complete. Brief saved to `marketing/brainstorms/[filename]`. Run `/cmo` to execute the next step (`/[next-skill]`), or invoke `/<next

People who liked this also viewed

6 picks

Type

brainstorm

27stars5forks

View on GitHub

How to install brainstorm?

moizibnyousaf/marketing-cli/brainstorm

$npx -y skills add MoizIbnYousaf/marketing-cli --skill brainstorm

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /brainstorm — Marketing Brainstorm
2
3	Structured exploration when marketing direction is unclear. You produce a brief that tells /cmo where to route next.
4
5	For brand memory protocol, see /cmo [rules/brand-memory.md](../cmo/rules/brand-memory.md).
6
7	## On Activation
8
9	1. Read `brand/` files if they exist (voice-profile.md, audience.md, positioning.md, learnings.md). They enhance but never gate.
10	2. Assess the user's request clarity level.
11
12	## Phase 0: Assess Clarity
13
14	Gate check. If the request is already specific, skip brainstorming:
15
16	\| Signal \| Action \|
17	\|--------\|--------\|
18	\| "Write a landing page for X" \| Skip. Route to `direct-response-copy`. \|
19	\| "Do SEO for my blog" \| Skip. Route to `keyword-research`. \|
20	\| "I want to market my app" \| Proceed. Multiple valid paths. \|
21	\| "What should I do next?" \| Proceed. No clear direction. \|
22	\| "Help me think through our launch" \| Proceed. Needs exploration. \|
23
24	If skipping: "Your request is specific enough to execute directly. Routing to `/<skill>` instead of brainstorming."
25
26	## Phase 1: Understand the Challenge
27
28	Ask ONE question at a time. Prefer multiple choice when natural options exist. Skip questions already answered by brand/ context.
29
30	Questions to cover (in order, stop when clear):
31
32	1. Goal — What are you trying to achieve? (awareness / leads / revenue / retention / launch)
33	2. Product — What are you marketing? (Brief description if not obvious from project context)
34	3. Audience — Who buys this? (Skip if `brand/audience.md` exists and is current — confirm briefly instead: "Your audience profile says X. Still accurate?")
35	4. Channels — Where does your audience hang out? (search / social / email / communities / paid)
36	5. Constraints — Budget, timeline, team size, tools available?
37	6. Competition — Who else does this? What makes you different? (Skip if `brand/competitors.md` exists — reference it instead)
38
39	Stop as soon as you have enough to propose approaches. 3-4 questions is usually enough.
40
41	## Phase 2: Explore Approaches
42
43	Present 2-3 concrete strategic directions. For each:
44
45	```
46	### Approach [N]: [Name]
47
48	Core angle: [One sentence positioning]
49	Channels: [Primary → Secondary]
50	Audience fit: [Why this resonates with the target]
51	Timeline: [Quick win vs. long play]
52	Pros: [2-3 bullet points]
53	Cons: [1-2 bullet points]
54	Best when: [Conditions that make this the right choice]
55	```
56
57	Ask the user to pick one, combine elements, or explore further.
58
59	Handling responses:
60
61	\| User says \| Action \|
62	\|-----------\|--------\|
63	\| Picks an approach \| Move to Phase 3 with that approach \|
64	\| Wants to combine \| Merge the relevant elements into a hybrid approach, confirm the blend, then move to Phase 3 \|
65	\| Rejects all approaches \| Ask what felt wrong. Probe for the constraint or preference you missed. Generate 1-2 new approaches informed by their feedback \|
66	\| "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 \|
67	\| Wants to explore further \| Ask one targeted follow-up question, then generate 1-2 additional approaches \|
68
69	## Phase 3: Capture Marketing Brief
70
71	Write a structured brief to `marketing/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`:
72
73	```markdown
74	---
75	type: marketing-brainstorm
76	date: YYYY-MM-DD
77	topic: [kebab-case topic]
78	goal: [awareness\|leads\|revenue\|retention\|launch]
79	chosen-approach: [N]
80	---
81
82	# Marketing Brief: [Topic]
83
84	## Context
85	[What we're marketing and why now]
86
87	## Chosen Approach
88	[Selected direction with rationale]
89
90	## Target Audience
91	[Who we're reaching]
92
93	## Channels
94	[Primary and secondary channels]
95
96	## Key Messages
97	[3-5 core messages]
98
99	## Constraints
100	[Budget, timeline, tools]
101
102	## Success Metrics
103	[How we'll measure impact]
104
105	## Structured Handoff
106	next-skill: [skill-name]
107	confidence: [high\|medium\|low]
108	context-summary: "[One line summary for /cmo routing]"
109	```
110
111	The `next-skill` field is critical — it tells /cmo where to route after brainstorming.
112
113	## Phase 4: Route Back to /cmo
114
115	After writing the brief:
116
117	"The brainstorm is complete. Brief saved to `marketing/brainstorms/[filename]`. Run `/cmo` to execute the next step (`/[next-skill]`), or invoke `/<next

People who liked this also viewed

6 picks

Type