brainstorming

Guide brainstorming into structured design documents with approval gates.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Phife726/ds_agent --skill brainstorming-phife726
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Phife726/ds_agent/tree/main/brainstorming
Command: npx skills add https://github.com/Phife726/ds_agent --skill brainstorming-phife726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming ideas into designs helps ensure deliberate exploration of intent, requirements, and design direction before any implementation, reducing risk of scope creep and rework.

Core Features & Use Cases

  • Explore project context — review files, docs, and recent commits to ground the discussion.
  • Ask clarifying questions — one focused question at a time to refine purpose and success criteria.
  • Propose 2-3 approaches — outline trade-offs and recommendations for how to realize the idea.
  • Present design — deliver structured design sections and obtain approval before proceeding.
  • Write design doc — generate a formal plan and document the decisions.
  • Transition to implementation — hand off to implementation planning when design is approved.

Quick Start

Begin by outlining the project context and asking one clarifying question to refine the goal.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I convert vague product ideas into structured design directions?

Brainstorming design directions requires exploring project context like files and recent commits, then asking focused clarifying questions one at a time to validate concepts before proposing approaches and documenting decisions.

What is the best way to run early-stage concept validation for feature development?

Early-stage concept validation uses guided brainstorming to review project context, ask targeted clarifying questions, and propose 2-3 approaches with trade-offs, ensuring deliberate exploration of intent before implementation.

How do I generate a formal design doc with approval gates before implementation?

Generate a formal design doc by presenting structured design sections for approval after brainstorming approaches, then writing the documented decisions and transitioning to implementation planning only when design is approved.

Do I need existing project files and docs to start a cross-functional design session?

Existing project files, docs, and recent commits are needed to ground cross-functional design sessions, as brainstorming starts by outlining project context and reviewing these materials before asking clarifying questions.

How to reduce scope creep and rework during product design planning?

Reduce scope creep and rework by using brainstorming to ensure deliberate exploration of intent, requirements, and design direction before implementation, applying approval gates to formal design documentation.