brainstorming

Run structured brainstorming sessions to produce validated design docs before coding.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/billh93/snchz --skill brainstorming-billh93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/billh93/snchz/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/billh93/snchz --skill brainstorming-billh93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This brainstorming workflow provides a structured approach to exploring project context, asking clarifying questions, and framing design options before any implementation effort, reducing misalignment and rework.

Core Features & Use Cases

  • Structured context exploration: Understand project goals, constraints, and risks before starting design.
  • Guided questioning: Ask one focused clarifying question at a time to refine requirements.
  • Design options & docs: Generate 2-3 approaches with trade-offs and produce a design doc for approval.
  • Transition to implementation: Prepare for handoff by creating a written design and planning the next steps.

Quick Start

Begin by clarifying the project goal and constraints, then step through questions to shape a design before coding.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I structure a brainstorming session to produce a validated design doc before coding?

To structure a brainstorming session for a validated design doc, start by exploring project context and constraints, then ask focused clarifying questions one at a time. Generate 2-3 design approaches with trade-offs before finalizing the design doc for implementation handoff.

What is the best way to align team requirements during product ideation?

Aligning team requirements during product ideation requires guided questioning, asking one focused clarifying question at a time to refine project goals and mitigate risks, ultimately reducing misalignment and rework before implementation begins.

How does exploring project context reduce rework in design collaboration?

Exploring project context reduces rework in design collaboration by uncovering goals, constraints, and risks upfront. This structured approach ensures all stakeholders share alignment before generating design options and committing to implementation.

Can I generate multiple design approaches with trade-offs before implementation planning?

Yes, you can generate 2-3 design approaches with trade-offs during the brainstorming workflow. This structured ideation phase evaluates options against project constraints before culminating in a formal design doc for implementation handoff.

Do I need a formal design doc to transition from ideation to implementation?

Yes, a formal design doc is required to transition from ideation to implementation. It captures the validated plan, approved approaches, and project context, serving as the written foundation for planning next steps and handoff.

What limitations exist when using a structured brainstorming workflow for product management?

The structured brainstorming workflow requires strict adherence to a SKILL.md frontmatter specification and focuses heavily on upfront design validation, meaning it may not suit projects needing immediate, unstructured prototyping without formal design documentation.