brainstorm

Coordinate structured design sessions to explore open-feature ideas.

6|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/nesquikm/dev-process-toolkit --skill brainstorm-nesquikm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/brainstorm
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill brainstorm-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate structured design sessions to explore open-feature ideas and align on a preferred approach.

Core Features & Use Cases

  • Guides teams through Socratic, one-question-at-a-time exploration to clarify goals.
  • Produces 2–3 viable design approaches with tradeoffs and risks for fast alignment.
  • Ready-to-hand-off input for /dev-process-toolkit:spec-write once a decision is made.

Quick Start

Instruct the system to run a brainstorming session for a feature and capture the resulting design direction.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I run a structured brainstorming session for open feature ideas?

Structured brainstorming for open features is facilitated through Socratic, one-question-at-a-time exploration to clarify goals, generate 2–3 design approaches, and obtain explicit design approval before spec-writing.

What is the best way to explore design approaches and align on product decisions?

Exploring design approaches during early product discovery is best achieved by producing 2–3 viable options with tradeoffs and risks, enabling fast team alignment on a preferred approach before writing specifications.

How do I clarify product goals before writing a feature specification?

Product goals are clarified using one-at-a-time questioning during early product discovery, ensuring explicit decisions are captured and a clean hand-off is prepared for the spec-write flow.

Can I use this Socratic design session to generate tradeoffs and risks for product management?

Socratic design sessions can be used for product management to generate 2–3 viable design approaches, explicitly detailing tradeoffs and risks to ensure fast alignment on the feature direction.

When do I need a Socratic design session for product ideation?

A Socratic design session for product ideation is needed during early product discovery to explore open-feature ideas, clarify goals, and obtain design approval before transitioning into spec-writing.