Skip to content
cccskills
FreePublished on GitHub

brainstorming

Transform rough ideas into solid designs through structured questioning

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Brainstorming → Design

Purpose

Turn vague ideas into actionable designs through Socratic questioning.

"I'm using the Brainstorming skill to refine your idea into a design."

The Flow

[Idea] → Phase 1: Understand → Phase 2: Explore → Phase 3: Design → [Plan]

Phase 1: Understanding (Ask Questions)

One question at a time. Prefer multiple choice.

Questions to ask:

  • What problem does this solve?
  • Who's the user?
  • What's success look like?
  • Any constraints (time, tech, integrations)?
  • What's already built that this touches?

Before asking: Check working directory for existing context.

Phase 2: Exploration (Present Options)

Present 2-3 approaches:

### Approach A: [Name]
- Architecture: [how it works]
- Pros: [benefits]
- Cons: [tradeoffs]
- Complexity: [low/medium/high]

### Approach B: [Name]
...

Ask: "Which approach resonates? Or should we explore others?"

Phase 3: Design (Incremental)

Present design in 200-300 word chunks:

  1. Architecture overview
  2. Key components
  3. Data flow
  4. Error handling
  5. Testing strategy

After each chunk: "Does this look right?"

Phase 4: Handoff

When design approved:

"Ready to create the implementation plan?"

If yes → Use writing-plans skill

Going Backwards

It's okay to revisit earlier phases:

  • New constraint discovered → Back to Phase 1
  • Design doesn't feel right → Back to Phase 2
  • Missing requirements → Back to Phase 1

Don't force linear progress.

Principles

  • YAGNI - Don't design what's not needed
  • Explore alternatives - Never settle on first idea
  • Validate incrementally - Small chunks, frequent feedback
  • Document decisions - Why, not just what

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

Canvas API Connection Skill

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.

The English summary is being prepared. Showing the original description.

a-ariff/ariff-claude-plugins14Updated Mar 29, 2026

See all skills by a-ariff

Report a problem with this skill