brainstorming

Name: brainstorming
Author: aaddrick

120stars16forks

How to install brainstorming?

aaddrick/claude-pipeline/brainstorming

$npx -y skills add aaddrick/claude-pipeline --skill brainstorming

Installs into the current project.

Summary

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Files · 1

View on GitHub

SKILL.md

1	# Brainstorming Ideas Into Designs
2
3	## Overview
4
5	Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
6
7	Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
8
9	## The Process
10
11	Understanding the idea:
12	- Check out the current project state first (files, docs, recent commits)
13	- Ask questions one at a time to refine the idea
14	- Prefer multiple choice questions when possible, but open-ended is fine too
15	- Only one question per message - if a topic needs more exploration, break it into multiple questions
16	- Focus on understanding: purpose, constraints, success criteria
17
18	Exploring approaches:
19	- Propose 2-3 different approaches with trade-offs
20	- Present options conversationally with your recommendation and reasoning
21	- Lead with your recommended option and explain why
22
23	Presenting the design:
24	- Once you believe you understand what you're building, present the design
25	- Break it into sections of 200-300 words
26	- Ask after each section whether it looks right so far
27	- Cover: architecture, components, data flow, error handling, testing
28	- Be ready to go back and clarify if something doesn't make sense
29
30	## After the Design
31
32	Documentation:
33	- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
34	- Use elements-of-style:writing-clearly-and-concisely skill if available
35	- Commit the design document to git
36
37	Implementation (if continuing):
38	- Ask: "Ready to set up for implementation?"
39	- Use using-git-worktrees to create isolated workspace
40	- Use writing-plans to create detailed implementation plan
41
42	## Key Principles
43
44	- One question at a time - Don't overwhelm with multiple questions
45	- Multiple choice preferred - Easier to answer than open-ended when possible
46	- YAGNI ruthlessly - Remove unnecessary features from all designs
47	- Explore alternatives - Always propose 2-3 approaches before settling
48	- Incremental validation - Present design in sections, validate each
49	- Be flexible - Go back and clarify when something doesn't make sense

People who liked this also viewed

6 picks

Type

brainstorming

120stars16forks

View on GitHub

How to install brainstorming?

aaddrick/claude-pipeline/brainstorming

$npx -y skills add aaddrick/claude-pipeline --skill brainstorming

Installs into the current project.

Summary

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Files · 1

View on GitHub

SKILL.md

1	# Brainstorming Ideas Into Designs
2
3	## Overview
4
5	Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
6
7	Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
8
9	## The Process
10
11	Understanding the idea:
12	- Check out the current project state first (files, docs, recent commits)
13	- Ask questions one at a time to refine the idea
14	- Prefer multiple choice questions when possible, but open-ended is fine too
15	- Only one question per message - if a topic needs more exploration, break it into multiple questions
16	- Focus on understanding: purpose, constraints, success criteria
17
18	Exploring approaches:
19	- Propose 2-3 different approaches with trade-offs
20	- Present options conversationally with your recommendation and reasoning
21	- Lead with your recommended option and explain why
22
23	Presenting the design:
24	- Once you believe you understand what you're building, present the design
25	- Break it into sections of 200-300 words
26	- Ask after each section whether it looks right so far
27	- Cover: architecture, components, data flow, error handling, testing
28	- Be ready to go back and clarify if something doesn't make sense
29
30	## After the Design
31
32	Documentation:
33	- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
34	- Use elements-of-style:writing-clearly-and-concisely skill if available
35	- Commit the design document to git
36
37	Implementation (if continuing):
38	- Ask: "Ready to set up for implementation?"
39	- Use using-git-worktrees to create isolated workspace
40	- Use writing-plans to create detailed implementation plan
41
42	## Key Principles
43
44	- One question at a time - Don't overwhelm with multiple questions
45	- Multiple choice preferred - Easier to answer than open-ended when possible
46	- YAGNI ruthlessly - Remove unnecessary features from all designs
47	- Explore alternatives - Always propose 2-3 approaches before settling
48	- Incremental validation - Present design in sections, validate each
49	- Be flexible - Go back and clarify when something doesn't make sense

People who liked this also viewed

6 picks

Type