brainstorming

Convert vague product requests into user-approved design specifications.

Updated Mar 27, 2026

Search Tags:#design #brainstorming #requirements #handoff #spec-writing #clarifying-questions #visual-support

Ready to run

npx skills add https://github.com/quanpersie2001/pulse --skill brainstorming-quanpersie2001

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/brainstorming
Command: npx skills add https://github.com/quanpersie2001/pulse --skill brainstorming-quanpersie2001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Converts vague or underspecified requests into a validated, user-approved design specification so implementation does not start on unstabilized assumptions or missing requirements.

Core Features & Use Cases

Structured clarifying flow: Ask one question at a time, surface constraints and success criteria, and avoid batching questions that hide latent requirements.
Alternative proposals & incremental validation: Present 2–3 approaches with trade-offs, lead with a recommendation, and present the design in sections asking for approval after each section.
Visual support & runtime: Optionally offer visual previews or start a local visual runtime for layout and hierarchy decisions, capturing browser selections back into the session.
Spec delivery & handoff: Write the approved spec to history/<feature>/spec.md, run an automated subagent self-review, update .pulse/STATE.md, and hand off to pulse:exploring without invoking planning or execution.

Quick Start

Use the brainstorming skill to turn a vague feature request into a short approved spec and save it to history/<feature>/spec.md.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn a vague product request into a design specification?▼

To convert a vague product request into a design specification, use a structured clarifying flow that asks one question at a time to surface constraints, presents 2-3 alternative proposals with trade-offs, and saves the approved design spec to history/<feature>/spec.md.

What is the best way to gather requirements before feature implementation?▼

The best way to gather requirements before feature implementation is to enforce an incremental validation process, presenting design sections for user approval sequentially and avoiding batched questions that hide latent requirements.

Does this brainstorming workflow support visual previews for layout decisions?▼

Yes, the brainstorming workflow optionally launches a local visual preview runtime to evaluate layout and hierarchy decisions, capturing browser selections directly back into the active design session.

Do I need Node.js to run the visual preview runtime for spec writing?▼

Yes, you need Node.js installed as a dependency to optionally launch the local visual preview runtime and execute the associated scripts during the design specification process.

How are finalized design specs handed off after clarifying questions?▼

Finalized design specs are handed off by writing the approved document to history/<feature>/spec.md, running an automated subagent self-review, updating the .pulse/STATE.md file, and transferring context to pulse:exploring without triggering planning or execution.

When should I not use an incremental design spec workflow?▼

You should not use an incremental design spec workflow during late-stage implementation or execution phases, as this process is designed strictly for early-stage feature design, architecture decisions, scoping, and evaluation tasks before planning begins.