brainstorming

Name: brainstorming
Availability: InStock
Author: hetsheth-droid

Guide teams through requirement discovery and design before implementation.

Updated Mar 31, 2026

Search Tags:#design #brainstorming #ideation #specification #requirements #design-first

Ready to run

npx skills add https://github.com/hetsheth-droid/toolbox-template --skill brainstorming-hetsheth-droid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/superpowers-skills/brainstorming
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill brainstorming-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps clarify user intent, requirements, and design constraints before any implementation, reducing revisits and misalignment.

Core Features & Use Cases

Structured inquiry: ask clarifying questions one at a time to refine the idea.
Design-first workflow: present the design and secure user approval before any coding or scaffolding.
Guardrails: enforce gates to prevent premature implementation.

Quick Start

Provide a project context and ask one clarifying question at a time to shape the design before drafting specifications.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I gather requirements and define scope before starting implementation?▼

To gather requirements before implementation, guide the team through structured inquiry by asking clarifying questions one at a time. This requirement discovery process refines the initial idea and defines scope, risks, and success criteria.

What is a design-first workflow for product and UX initiatives?▼

A design-first workflow presents the design and secures explicit user approval before any coding or scaffolding begins. This approach enforces approval gates to prevent premature implementation and reduce project misalignment.

Why does my team keep revisiting scope and misaligning on software specifications?▼

Teams revisit scope and misalign on specifications because user intent and design constraints were not clarified beforehand. Structured questioning during ideation clarifies constraints early, reducing the need for later revisits.

Can I use structured ideation for both product software and UX design projects?▼

Yes, you can use structured ideation for product, software, and UX initiatives. The process applies whenever understanding user intent and constraints is critical to defining success criteria before transitioning to implementation planning.

What's the best way to prevent premature coding during project ideation?▼

The best way to prevent premature coding during ideation is to enforce guardrails with explicit approval gates. Secure design approval first, ensuring the team only transitions to implementation planning after the design is fully approved.

When should I not use a design-first ideation process?▼

You should not use a design-first ideation process when implementation must begin immediately without defining scope or success criteria. If understanding user intent and constraints is not critical, skipping structured questioning may be acceptable.