From quick-review
This skill should be used when the user asks to "brainstorm", "find ideas", "explore approaches", or explicitly wants multiple perspectives on a problem before deciding.
How this skill is triggered — by the user, by Claude, or both
Slash command
/quick-review:brainstormThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user wants to brainstorm, launch 3 subagents in parallel using the Task tool. Each agent explores the problem from a different perspective.
When the user wants to brainstorm, launch 3 subagents in parallel using the Task tool. Each agent explores the problem from a different perspective.
subagent_type: "general-purpose"model: "haiku" for cost-effectiveness (exploratory work)Personality: Thinks about pain points, bounds, what scenarios to avoid, and only then thinks how to address those.
Prompt template:
Problem: [user's problem in their words]
Analyze from a defensive perspective. List:
1. Pain points and constraints
2. Bounds (technical, time, resources)
3. Scenarios that must be avoided
Then suggest approaches that address these concerns.
Personality: Tries finding solutions that use as little code as possible.
Prompt template:
Problem: [user's problem in their words]
Find the simplest solution. Consider:
1. The absolute minimum code needed
2. Existing tools/libraries that could handle this
3. What can be deleted or avoided entirely
Propose the leanest viable approach.
Personality: A battle-seasoned CTO who knows how things go wrong.
Prompt template:
Problem: [user's problem in their words]
Review with experience-earned skepticism. Identify:
1. Where this will break in production
2. Edge cases that will bite us later
3. What looks simple but isn't
State what you'd insist on if this was your company.
User: "Let's brainstorm how to add caching to the API"
Launch 3 Task agents in parallel:
After collecting all 3 perspectives, present a synthesis:
npx claudepluginhub hibukki/yonatans-cc-marketplace --plugin quick-reviewGuides structured brainstorming with research, codebase exploration, and cross-domain thinking. Activates on open-ended problems or brainstorming prompts.
Guides structured brainstorming to clarify user intent, explore approaches, trade-offs, and refine requirements before implementing features or changes. Activates on ambiguous requests.
Guides collaborative brainstorming to refine fuzzy requirements, explore implementation alternatives, and form designs before coding.