Skip to content
cccskills
FreePublished on GitHub

Brainstorming Ideas Into Designs

Interactive idea refinement using Socratic method to develop fully-formed designs

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

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Brainstorming Ideas Into Designs

Overview

Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.

Core principle: Ask questions to understand, explore alternatives, present design incrementally for validation.

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

The Process

Phase 1: Understanding

  • Check current project state in working directory
  • Ask ONE question at a time to refine the idea
  • Prefer multiple choice when possible
  • Gather: Purpose, constraints, success criteria

Phase 2: Exploration

  • Propose 2-3 different approaches (reference skills/coding/exploring-alternatives)
  • For each: Core architecture, trade-offs, complexity assessment
  • Ask your human partner which approach resonates

Phase 3: Design Presentation

  • Present in 200-300 word sections
  • Cover: Architecture, components, data flow, error handling, testing
  • Ask after each section: "Does this look right so far?"

Phase 4: Worktree Setup (for implementation)

When design is approved and implementation will follow:

  • Announce: "I'm using the Using Git Worktrees skill to set up an isolated workspace."
  • Switch to skills/collaboration/using-git-worktrees
  • Follow that skill's process for directory selection, safety verification, and setup
  • Return here when worktree ready

Phase 5: Planning Handoff

Ask: "Ready to create the implementation plan?"

When your human partner confirms (any affirmative response):

  • Announce: "I'm using the Writing Plans skill to create the implementation plan."
  • Switch to skills/collaboration/writing-plans skill
  • Create detailed plan in the worktree

Remember

  • One question per message during Phase 1
  • Apply YAGNI ruthlessly (reference skills/architecture/reducing-complexity)
  • Explore 2-3 alternatives before settling
  • Present incrementally, validate as you go
  • Announce skill usage at start

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

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

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

obra/clank42Updated Oct 10, 2025

Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)

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

obra/clank42Updated Oct 10, 2025

Replace arbitrary timeouts with condition polling for reliable async tests

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

obra/clank42Updated Oct 10, 2025

TDD for process documentation - test with subagents before writing, iterate until bulletproof

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

obra/clank42Updated Oct 10, 2025

Validate at every layer data passes through to make bugs impossible

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

obra/clank42Updated Oct 10, 2025

Design in pseudocode first, iterate approaches, then translate to code

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

obra/clank42Updated Oct 10, 2025

See all skills by obra

Report a problem with this skill