brainstorm

Name: brainstorm
Author: tranhieutt

69stars41forks

How to install brainstorm?

tranhieutt/software_development_department/brainstorm

$npx -y skills add tranhieutt/software_development_department --skill brainstorm

Installs into the current project.

Summary

Facilitates structured product ideation to define user needs, core value, and product direction. Use when the user wants to explore a new product idea, has a vague concept to develop, or mentions brainstorming or ideation.

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Parse the argument for an optional product type or problem hint (e.g., `productivity app`,
4	`API service`, `developer tool`, `marketplace`). If `open` or no argument, start from scratch.
5
6	2. Check for existing concept work:
7	- Read `design/docs/product-concept.md` if it exists (resume, don't restart)
8	- Read `design/docs/product-pillars.md` if it exists (build on established pillars)
9
10	3. Run through ideation phases interactively, asking the user questions at
11	each phase. Do NOT generate everything silently — the goal is **collaborative
12	exploration** where the AI acts as a product thinking facilitator, not a
13	replacement for the human's vision.
14
15	Use `AskUserQuestion` at key decision points throughout brainstorming:
16	- Constrained taste questions (product type, target users, scope)
17	- Concept selection ("Which 2-3 concepts resonate?") after presenting options
18	- Direction choices ("Develop further, explore more, or start sprint planning?")
19	- Pillar ranking after concepts are refined
20
21	Write full analysis in conversation text first, then use `AskUserQuestion`
22	to capture the decision with concise labels.
23
24	Professional product brainstorming principles to follow:
25	- Withhold judgment — no idea is bad during exploration
26	- Encourage unusual ideas — outside-the-box thinking sparks better products
27	- Build on each other — "yes, and..." responses, not "but..."
28	- Use constraints as creative fuel — limitations often produce the best ideas
29	- Time-box each phase — keep momentum, don't over-deliberate early
30
31	---
32
33	### Phase 1: Creative Discovery
34
35	Start by understanding the person and their context, not the product. Ask these questions
36	conversationally (not as a checklist):
37
38	Problem anchors:
39	- What's a frustrating problem you personally experience that no existing tool solves well?
40	- Is there a workflow, process, or task you've always wished was easier or more automated?
41
42	Experience profile:
43	- What 3 products (apps, tools, APIs, services) do you use most? What keeps you coming back?
44	- Are there product categories you love or actively avoid? Why?
45	- Do you prefer products that save time, reduce complexity, enable creativity, or connect people?
46
47	Practical constraints (shape the sandbox before brainstorming):
48	- Solo developer or team? What skills and resources are available?
49	- Timeline: weeks (MVP), months (v1), or years (full product)?
50	- Any platform constraints? (Web only? Mobile? API-first? Desktop?)
51	- First product or experienced builder?
52	- Revenue model in mind? (SaaS, open source, freemium, one-time purchase?)
53
54	Synthesize the answers into a Product Brief — a 3-5 sentence
55	summary of the person's goals, experience context, and constraints.
56	Read the brief back and confirm it captures their intent.
57
58	---
59
60	### Phase 2: Concept Generation
61
62	Using the product brief as a foundation, generate 3 distinct concepts
63	that each take a different creative direction. Use these ideation techniques:
64
65	Technique 1: Verb-First Design
66	Start with the core user verb (build, track, automate, connect, analyze, manage,
67	discover, share, deploy) and build the product outward from there. The verb IS the product.
68
69	Technique 2: Problem-Inversion Method
70	Take an existing frustration in a market and invert it. "What if [pain point] just...
71	didn't exist?" Then design backward from that ideal state. Find the simplest product
72	that bridges the current reality to that ideal.
73
74	Technique 3: Intersection Design
75	Combine two unexpected domains: [Audience A] + [Workflow B]. The intersection creates
76	the unique hook. (e.g., "developers + financial compliance", "designers + data pipelines",
77	"small teams + enterprise security")
78
79	For each concept, present:
80	- Working Title
81	- Elevator Pitch (1-2 sentences — must pass the "10-second test")
82	- Core User Action (the single most frequent thing a user does)
83	- Core Value Promise (the outcome users pay/sign-up for)
84	- Unique Angle (passes the "AND ALSO" test: "Like X, AND ALSO Y")
85	- Target User (who specifically? Not "developers" — "backend engineers at 50-person startups")
86	- Estimated Scope (small / medium / large)
87	- Why It Could Work (1 sentence on market/timing fit)
88	- Biggest Risk (1 sentence on the hardest unanswered question)
89
90	Present all three. Ask the user t

People who liked this also viewed

6 picks

Type

brainstorm

69stars41forks

View on GitHub

How to install brainstorm?

tranhieutt/software_development_department/brainstorm

$npx -y skills add tranhieutt/software_development_department --skill brainstorm

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Parse the argument for an optional product type or problem hint (e.g., `productivity app`,
4	`API service`, `developer tool`, `marketplace`). If `open` or no argument, start from scratch.
5
6	2. Check for existing concept work:
7	- Read `design/docs/product-concept.md` if it exists (resume, don't restart)
8	- Read `design/docs/product-pillars.md` if it exists (build on established pillars)
9
10	3. Run through ideation phases interactively, asking the user questions at
11	each phase. Do NOT generate everything silently — the goal is **collaborative
12	exploration** where the AI acts as a product thinking facilitator, not a
13	replacement for the human's vision.
14
15	Use `AskUserQuestion` at key decision points throughout brainstorming:
16	- Constrained taste questions (product type, target users, scope)
17	- Concept selection ("Which 2-3 concepts resonate?") after presenting options
18	- Direction choices ("Develop further, explore more, or start sprint planning?")
19	- Pillar ranking after concepts are refined
20
21	Write full analysis in conversation text first, then use `AskUserQuestion`
22	to capture the decision with concise labels.
23
24	Professional product brainstorming principles to follow:
25	- Withhold judgment — no idea is bad during exploration
26	- Encourage unusual ideas — outside-the-box thinking sparks better products
27	- Build on each other — "yes, and..." responses, not "but..."
28	- Use constraints as creative fuel — limitations often produce the best ideas
29	- Time-box each phase — keep momentum, don't over-deliberate early
30
31	---
32
33	### Phase 1: Creative Discovery
34
35	Start by understanding the person and their context, not the product. Ask these questions
36	conversationally (not as a checklist):
37
38	Problem anchors:
39	- What's a frustrating problem you personally experience that no existing tool solves well?
40	- Is there a workflow, process, or task you've always wished was easier or more automated?
41
42	Experience profile:
43	- What 3 products (apps, tools, APIs, services) do you use most? What keeps you coming back?
44	- Are there product categories you love or actively avoid? Why?
45	- Do you prefer products that save time, reduce complexity, enable creativity, or connect people?
46
47	Practical constraints (shape the sandbox before brainstorming):
48	- Solo developer or team? What skills and resources are available?
49	- Timeline: weeks (MVP), months (v1), or years (full product)?
50	- Any platform constraints? (Web only? Mobile? API-first? Desktop?)
51	- First product or experienced builder?
52	- Revenue model in mind? (SaaS, open source, freemium, one-time purchase?)
53
54	Synthesize the answers into a Product Brief — a 3-5 sentence
55	summary of the person's goals, experience context, and constraints.
56	Read the brief back and confirm it captures their intent.
57
58	---
59
60	### Phase 2: Concept Generation
61
62	Using the product brief as a foundation, generate 3 distinct concepts
63	that each take a different creative direction. Use these ideation techniques:
64
65	Technique 1: Verb-First Design
66	Start with the core user verb (build, track, automate, connect, analyze, manage,
67	discover, share, deploy) and build the product outward from there. The verb IS the product.
68
69	Technique 2: Problem-Inversion Method
70	Take an existing frustration in a market and invert it. "What if [pain point] just...
71	didn't exist?" Then design backward from that ideal state. Find the simplest product
72	that bridges the current reality to that ideal.
73
74	Technique 3: Intersection Design
75	Combine two unexpected domains: [Audience A] + [Workflow B]. The intersection creates
76	the unique hook. (e.g., "developers + financial compliance", "designers + data pipelines",
77	"small teams + enterprise security")
78
79	For each concept, present:
80	- Working Title
81	- Elevator Pitch (1-2 sentences — must pass the "10-second test")
82	- Core User Action (the single most frequent thing a user does)
83	- Core Value Promise (the outcome users pay/sign-up for)
84	- Unique Angle (passes the "AND ALSO" test: "Like X, AND ALSO Y")
85	- Target User (who specifically? Not "developers" — "backend engineers at 50-person startups")
86	- Estimated Scope (small / medium / large)
87	- Why It Could Work (1 sentence on market/timing fit)
88	- Biggest Risk (1 sentence on the hardest unanswered question)
89
90	Present all three. Ask the user t

People who liked this also viewed

6 picks

Type