BR

Facilitates collaborative design for underdefined technical tasks. Helps clarify requirements and tradeoffs before code is written.

Install

mkdir -p .claude/skills/brainstorming-tenecsson && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11105" && unzip -o skill.zip -d .claude/skills/brainstorming-tenecsson && rm skill.zip

Installs to .claude/skills/brainstorming-tenecsson

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when requirements, product choices, or technical approach are still underdefined and you need a design before implementation
128 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Translate open requests into designs
  • Identify architectural tradeoffs
  • Clarify underdefined requirements
  • Select implementation approaches

How it works

It uses a structured interview and trade-off analysis to guide the user toward an approved design before implementation begins.

Inputs & outputs

You give it
Open-ended technical or product request
You get back
Approved technical design

When to use brainstorming

  • Determine system architecture
  • Define feature scope and tradeoffs
  • Clarify underdefined requirements
  • Select implementation approaches

About this skill

Turn an open request into an approved design before coding.

Use this when:

  • success criteria, constraints, or tradeoffs are still unclear
  • the user wants help choosing architecture, behavior, or scope

Do not use this when:

  • an approved design or implementation plan already exists
  • the request is status, review, or verification only
  • the patch is narrow and the desired behavior is already specified

Workflow:

  1. Scan only the context needed to understand the problem.
  2. Ask one clarifying question at a time. Prefer multiple choice when it genuinely helps.
  3. If the design is open, present 2-3 approaches with tradeoffs and a recommendation. If it is bounded, present one recommended approach.
  4. Describe the design at the right level: architecture, data flow, edge cases, and tests.
  5. Get approval before implementation.
  6. Write docs/plans/YYYY-MM-DD-<topic>-design.md only if the design needs durable reuse, review, or handoff.
  7. If execution still needs a multi-step plan, switch to writing-plans. Otherwise implement directly.

Principles:

  • Do not implement while material design questions remain open.
  • Resolve real uncertainty, not imaginary uncertainty.
  • Use the lightest process that closes the gap.
  • Cut unneeded features early.

When not to use it

  • When an approved design already exists
  • For status, review, or verification tasks

Limitations

  • Requires user approval before coding
  • Not for narrow, well-specified patches

How it compares

It forces a design phase for underdefined requests, preventing premature implementation.

Compared to similar skills

brainstorming side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
brainstorming (this skill)04moNo flagsIntermediate
brainstorming934moReviewBeginner
spec-workflow108moNo flagsIntermediate
feature-design-assistant67moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry