brainstorming

Facilitate structured brainstorming to convert user intent into a design spec.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/pcsensor/serial --skill brainstorming-pcsensor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/pcsensor/serial/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/pcsensor/serial --skill brainstorming-pcsensor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn fuzzy ideas into a concrete design plan by guiding exploratory dialogue, capturing requirements, and prioritizing actions before any implementation.

Core Features & Use Cases

  • Structured exploration prompts to reveal intent, constraints, and success criteria.
  • 2–3 design options with trade-offs and a recommended path.
  • A documented design plan saved as a detailed spec for review and sign-off. Use cases include early discovery for product features, architecture decisions, and user flows where clarity is essential.

Quick Start

Describe the high-level goal you want to achieve with the next product feature and let the brainstorm guide you to a validated spec.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn fuzzy product ideas into a clear design spec?

Structured brainstorming turns fuzzy ideas into a clear design spec by facilitating exploratory dialogue to extract user intent, constraints, and success criteria. It converts these insights into a formal design document for team review and sign-off.

What is the best way to document design trade-offs during ideation?

Documenting design trade-offs during ideation requires proposing 2-3 design options with explicit trade-offs and a recommended path. This maintains project scope and ensures acceptance criteria are documented before creating an implementation plan.

How do I extract requirements for early product feature discovery?

Extract requirements for early feature discovery by using structured exploration prompts that reveal user intent, constraints, and success criteria. This prioritizes actions and guides the design process before any implementation begins.

Does this ideation process work for architecture decisions and user flows?

Yes, this ideation process works for architecture decisions and user flows. It guides exploratory dialogue and captures requirements specifically for early discovery contexts where design clarity is essential before implementation.

When should I not use structured brainstorming for design planning?

Avoid structured brainstorming when you need to skip trade-off exploration or avoid documenting acceptance criteria. The process enforces these guardrails to maintain scope before generating any implementation plan.