brainstorming

Guide ambiguous software decisions into structured design specifications before implementation.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/JiangAustin/Money_Never_Sleep --skill brainstorming-jiangaustin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/JiangAustin/Money_Never_Sleep/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/JiangAustin/Money_Never_Sleep --skill brainstorming-jiangaustin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature implementation by turning vague requests into clear, validated designs before any code is written. It helps teams avoid rework when building new features, changing behavior, or shaping product direction.

Core Features & Use Cases

  • Context Exploration: Reviews the current project state, documentation, and recent changes to understand what already exists.
  • Guided Clarification: Asks one focused question at a time to uncover purpose, constraints, and success criteria.
  • Option Comparison: Presents 2 to 3 design approaches with tradeoffs and a recommendation so decisions are deliberate.
  • Specification Workflow: Converts the approved direction into a written spec, checks it for ambiguity or scope issues, and hands it off for implementation planning.
  • Use Case: A team wants to add a new workflow, UI behavior, or service boundary but has not settled the design yet; this Skill structures that conversation into an actionable plan.

Quick Start

Use the brainstorming skill to analyze the project context, ask me one clarifying question at a time, and help me produce an approved design spec before implementation.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague feature ideas into an approved design spec before implementation?

Turn vague feature ideas into an approved design spec by using a structured brainstorming workflow that explores project context, asks one clarifying question at a time, and compares 2-3 design approaches with tradeoffs before writing a specification.

What is the best way to structure product design brainstorming for ambiguous software decisions?

The best way to structure product design brainstorming for ambiguous software decisions is through guided clarification, comparing multiple design options with tradeoffs, and validating the direction at approval checkpoints before proceeding to implementation.

How do I plan a new workflow or UI behavior without writing code prematurely?

Plan a new workflow or UI behavior without writing code prematurely by reviewing existing project documentation, uncovering constraints through focused questions, and producing a written specification that hands off to implementation planning.

Can I compare 2 to 3 design approaches with tradeoffs for a new feature before building it?

Yes, you can compare 2 to 3 design approaches with tradeoffs and a recommendation to ensure deliberate decisions, preventing rework when adding new features, changing behavior, or shaping product direction.

When should I use a structured brainstorming workflow for component planning instead of coding directly?

Use a structured brainstorming workflow for component planning when facing ambiguous software decisions that require clarification and tradeoff analysis, ensuring the team validates the design direction before any code is written.