brainstorming

Guide structured brainstorming to clarify requirements and explore implementation approaches.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/isndotbiz/website --skill brainstorming-isndotbiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/isndotbiz/website/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/isndotbiz/website --skill brainstorming-isndotbiz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps clarify user intent and explore different approaches for features or changes before implementation, preventing wasted effort on misunderstood requirements.

Core Features & Use Cases

  • Requirement Clarification: Asks targeted questions to understand the core problem, users, and success criteria.
  • Approach Exploration: Proposes 2-3 distinct implementation strategies with pros, cons, and best-use cases.
  • Design Summarization: Captures key decisions in a structured document for easy handoff to planning.
  • Use Case: When a user says "Let's build a better notification system," this skill will guide a conversation to define what "better" means, who it's for, and whether to use in-app, email, or both, before suggesting specific technical paths.

Quick Start

Use the brainstorming skill to explore ideas for a new user dashboard.

Frequently Asked Questions about brainstorming

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

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

Structured brainstorming clarifies product requirements by guiding you through requirement assessment, idea exploration, and design capture. It asks targeted questions to define scope, identify users, and evaluate trade-offs between different technical strategies before planning.

What is the best way to explore implementation approaches for a new feature?

Evaluating implementation approaches involves proposing 2-3 distinct technical strategies complete with pros, cons, and best-use cases. This structured exploration ensures you evaluate trade-offs between different technical strategies before proceeding to development.

How do I define the scope for a new user dashboard?

Defining scope for a new user dashboard involves guiding a conversation to establish what the feature means, who it is for, and its success criteria. This structured requirement assessment ensures alignment before suggesting specific technical paths.

Can I capture design decisions for handoff to planning?

Yes, you can capture design decisions for planning handoff by summarizing key choices in a structured document. This design summarization captures key decisions easily, ensuring alignment before proceeding to the actual planning phase.