skills.rest
rishikanthc
rishikanthcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

brainstorming

Turn ideas into validated design documents through iterative questioning.

Updated Feb 23, 2026
Search Tags:#design#planning#brainstorming#requirements#claude-code#task-management#design-doc
One-click install
npx skills add https://github.com/rishikanthc/ml-superpowers --skill brainstorming-rishikanthc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/rishikanthc/ml-superpowers/tree/main/skills/brainstorming
Command: npx skills add https://github.com/rishikanthc/ml-superpowers --skill brainstorming-rishikanthc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often proceed to implementation with unclear intent, hidden assumptions, or missing success criteria, causing rework and wasted effort; this Skill enforces a structured discovery process to define purpose, constraints, and an approvable design before any code is written.

Core Features & Use Cases

  • Structured context exploration: Inspect project files, docs, and recent commits to ground the conversation in the existing codebase.
  • Single-question iterative clarification: Ask one clarifying question at a time to converge on precise requirements and success criteria.
  • Options with trade-offs and recommended approach: Propose 2-3 approaches, explain trade-offs, and lead with a recommended solution.
  • Design validation and handoff: Present design sections for user approval, write the final design to docs/plans/YYYY-MM-DD-<topic>-design.md, commit it, and then invoke the writing-plans skill to create an implementation plan; integrates Claude Code native task creation and dependency tracking for handoff.
  • Use Case: Turning a rough feature request into an agreed-upon component design with explicit acceptance criteria and taskized implementation steps.

Quick Start

Ask one clarifying question about the feature's primary success criteria to begin turning the idea into an approved design.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a rough feature idea into a validated design document?▼

To create a design document from a feature idea, apply iterative questioning to clarify requirements and success criteria, propose multiple approaches with trade-offs, and save the approved design specs to a markdown file.

What is the best way to clarify requirements before starting component planning?▼

The best way to clarify requirements is single-question iterative clarification, asking one question at a time to converge on precise constraints and success criteria before proposing design approaches.

Can I generate task dependencies automatically after finalizing a design spec?▼

Yes, after finalizing a design document, you can generate task dependencies by invoking the writing-plans skill to create an implementation plan and integrate native task creation with dependency tracking for handoff.

Does this approach work for small to medium code changes or full project planning?▼

This design spec approach works specifically for small-to-medium code changes, feature design, and component planning where requirements, constraints, and success criteria must be clarified before implementation.

How do I compare different design approaches for a new feature?▼

To compare design approaches for a new feature, propose 2-3 solutions, explain the trade-offs of each, and lead with a recommended solution to guide selection during the design validation phase.

Where should I save the final design document for version control?▼

You should save the final design document to docs/plans/YYYY-MM-DD-<topic>-design.md and commit it to your repository to maintain version control and traceability before creating implementation tasks.

Related Skills

Explore More Product & Management Skills→
loianeloiane
50

brownfield-onboarding

Onboard an existing Spring codebase into a spec-driven workflow with baseline and design doc.

Community
Advanced
krzemienskikrzemienski
2

executing-plans

Execute implementation plans in batches with validation gates between batches.

Community
Intermediate
gvinokurgvinokur

implementer

Execute approved implementation plans into validated code with tests, lint, and builds.

Community
Advanced
hksloverhkslover
47

trellis-brainstorm

Structure ambiguous software requests into requirements and implementation plans.

Community
Advanced