brainstorming

Name: brainstorming
Availability: InStock
Author: Smooth-Operation

Clarify requirements by documenting approaches, trade-offs, and decision criteria.

Updated Jan 7, 2026

Search Tags:#brainstorming #requirements #feature planning #alignment #stakeholders #design-review

Ready to run

npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill brainstorming-smooth-operation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Smooth-Operation/household-expense-tracker/tree/main/.claude/skills/core/brainstorming
Command: npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill brainstorming-smooth-operation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify requirements through structured brainstorming.

Core Features & Use Cases

Provides a disciplined approach to exploring multiple design directions before committing to implementation.
Documents pros/cons, trade-offs, and decision criteria to align stakeholders.
Facilitates explicit go/no-go decisions to prevent scope creep.

Quick Start

Start a brainstorming session by restating the feature goal, listing 2-4 viable approaches, outlining trade-offs, and capturing explicit approval before coding.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I align stakeholders on feature planning before starting implementation?▼

Structured brainstorming clarifies ambiguous goals by documenting 2-4 viable approaches and capturing explicit go/no-go approval before coding. This process prevents scope creep by ensuring stakeholders align on decision criteria and trade-offs prior to implementation.

What is the best way to document trade-offs for major architectural changes?▼

The best way to document trade-offs for major architectural changes is to outline pros and cons alongside decision criteria during a structured brainstorming session. This captures multiple design directions and requires explicit approval before committing to implementation.

How do I run a design review for new features with multiple viable approaches?▼

Run a design review for new features by restating the feature goal, listing 2-4 viable approaches, and outlining trade-offs. Structured brainstorming facilitates this review by documenting options and capturing explicit go/no-go decisions to prevent scope creep.

When do I need structured brainstorming for requirements clarification?▼

You need structured brainstorming for requirements clarification when starting new features, tackling major architectural changes, or facing ambiguous goals where multiple approaches exist. It documents options and trade-offs to secure explicit stakeholder approval.

Can I prevent scope creep by requiring explicit approval before coding?▼

Yes, you can prevent scope creep by requiring explicit go/no-go approval before coding. Structured brainstorming enforces this disciplined approach by documenting pros, cons, and decision criteria to ensure stakeholders fully align on the chosen implementation direction.