brainstorming

Guide collaborative dialogue to refine ideas into approved design specs.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill brainstorming-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/workflow/brainstorming
Command: npx skills add https://github.com/ajsai47/holyclaude --skill brainstorming-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates wasted work from unexamined assumptions and premature implementation, which often plagues even seemingly "simple" projects like todo lists, single-function utilities, or config changes.

Core Features & Use Cases

  • Guided collaborative dialogue: Asks one clarifying question at a time to fully understand project purpose, constraints, and success criteria.
  • Mandatory design approval gate: Blocks all implementation actions (code writing, project scaffolding, etc.) until a full design is presented and explicitly approved by the user.
  • Optional visual companion: Supports browser-based mockups, diagrams, and visual comparisons for UI and design-related questions.
  • Written spec generation: Produces a committed design document and runs a self-review to catch placeholders, contradictions, and scope issues before implementation planning.
  • Use case: For example, if you want to add a new user notification system to your app, this skill will walk you through clarifying requirements, exploring 2-3 architectural approaches, and producing a written design spec for your approval before any code is written.

Quick Start

Use the brainstorming skill to turn your idea for a new todo list feature into a fully approved design before starting any implementation work.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I refine rough software ideas into validated design specifications?

To refine ideas into validated design specifications, use a structured collaborative dialogue process that requires a mandatory design approval gate and written spec documentation before any implementation work begins.

What is a pre-implementation review for feature development?

A pre-implementation review for feature development is a structured process that enforces design approval and written spec self-reviews to catch placeholders, contradictions, and scope issues before any coding starts.

How do I create a design specification before writing code?

Create a design specification before writing code by engaging in guided dialogue that fully understands project constraints, explores architectural approaches, and produces a committed design document awaiting explicit approval.

Does structured requirements gathering work for simple component building tasks?

Structured requirements gathering works for simple component building tasks by eliminating wasted work from unexamined assumptions through clarifying questions and mandatory design gates, regardless of perceived project simplicity.

What's the best way to prevent premature implementation in software development?

The best way to prevent premature implementation in software development is to block all code writing and project scaffolding actions until a full design is presented, self-reviewed for scope issues, and explicitly approved.

When do I need a written spec document for a functionality addition?

You need a written spec document for a functionality addition whenever you want to enforce a mandatory design approval gate, ensuring requirements gathering and architectural exploration are completed before implementation planning.