brainstorming

Clarify project requirements and produce a committed design document.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/eatbreads/.agents --skill brainstorming-eatbreads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/eatbreads/.agents/tree/main/skills/brainstorming
Command: npx skills add https://github.com/eatbreads/.agents --skill brainstorming-eatbreads

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents premature implementation by ensuring ideas are explored, assumptions are exposed, and requirements are validated before any code or scaffolding is written. It reduces wasted work caused by ambiguous goals, missed constraints, and unexamined edge cases.

Core Features & Use Cases

  • Structured discovery flow: Explore project context, ask one clarifying question at a time, and decompose large scopes into manageable sub-projects.
  • Decision support: Propose 2–3 alternative approaches with trade-offs and lead with a recommended option.
  • Design validation and handoff: Present the design in sections, get user approval, write a committed spec to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md, perform a self-review, and only then invoke implementation-planning.
  • Use Case: Planning a new feature, redesigning a UI flow, or making a configuration change where early clarification prevents rework.

Quick Start

Ask the brainstorming skill: "Help me design a user settings page for a mobile app, clarify constraints, propose 3 approaches with trade-offs, and produce a short design spec to commit."

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify feature requirements before starting implementation?

To clarify requirements before implementation, use a structured discovery flow that asks one question at a time, proposes 2-3 approaches with trade-offs, and produces a committed design document for user approval before coding begins.

What is the best way to write a design doc for a new UI feature?

Writing a design doc for a UI feature involves decomposing scope into manageable sub-projects, validating constraints iteratively through one-question-at-a-time clarification, and committing the finalized spec to a designated docs directory.

Can I use brainstorming to scope small configuration changes?

Yes, you can use brainstorming to scope small configuration changes. It applies to pre-implementation workflows including feature scoping, UI/UX decisions, small utilities, and configuration changes to define success criteria.

How do I avoid premature implementation when planning a project?

To avoid premature implementation, enforce iterative clarification and design validation before writing code. This prevents wasted work caused by ambiguous goals, missed constraints, and unexamined edge cases.

Does the design discovery process require user approval before planning?

Yes, the design discovery process requires explicit user approval. It presents the design in sections, performs a self-review, and only invokes implementation-planning after the committed design spec receives final user approval.