ss-brainstorming

Guide teams through question-driven brainstorming to refine design intent before coding.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Promotes Socratic, question-driven design refinement to understand intent, requirements, and constraints before implementation, reducing wasted effort from ambiguity or rushed decisions.

Core Features & Use Cases

  • Guided, one-question-at-a-time brainstorming to refine user needs and scope before writing any code or specs.
  • Complexity tier assessment (full vs light) with user prompts to determine the appropriate design depth.
  • Structured handoff to implementation: generates a design context and transitions to ss-writing-plans for concrete tasks and milestones.

Quick Start

Describe the change you want to make and initiate the guided brainstorming flow to produce a design proposal before implementation.

Frequently Asked Questions about ss-brainstorming

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

FAQPage Schema
How do I refine software requirements through brainstorming before writing code?

Refine software requirements through structured, one-question-at-a-time brainstorming dialogue to clarify intent and constraints, producing a design proposal before any implementation begins.

What's the best way to evaluate design trade-offs for an architectural change?

Evaluate design trade-offs by exploring 2-3 distinct approaches during a guided brainstorming session, assessing complexity tiers to determine the appropriate design depth for your architectural change.

When do I need a structured design doc for feature work?

You need a structured design doc for feature work or architectural changes involving multiple subsystems, using guided brainstorming to define scope and requirements before transitioning to implementation planning.

How do I transition from a brainstorming design to concrete implementation tasks?

Transition from brainstorming to implementation by generating a finalized design context that receives design approval, then handing off directly to a plan-writing process for concrete task and milestone creation.

Does this question-driven design approach work for both small features and large architectural changes?

Yes, the question-driven design approach works for both by assessing complexity tiers with user prompts, applying a full brainstorming flow for large changes or a light version for smaller features.