Verified:GitHub

brainstorming

Convert ambiguous feature ideas into an approved requirements spec for planning handoff.

Updated Apr 27, 2026

Search Tags:#brainstorming #product planning #scope safety #requirements spec #MVP discovery #evidence packet #decision gating

Ready to run

npx skills add https://github.com/vTRKA/supervibe --skill brainstorming-vtrka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/vTRKA/supervibe/tree/main/skills/brainstorming
Command: npx skills add https://github.com/vTRKA/supervibe --skill brainstorming-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents chaotic or premature coding sessions by transforming an ambiguous idea into an approved requirements spec before planning or implementation.

Core Features & Use Cases

Clarifies intent and scope: Captures the actual problem behind the request, including MVP boundaries, non-goals, risks, and kill criteria.
Selects the right brainstorm mode: Uses quick-idea for fast shaping, mvp-discovery for PRD-ready discovery, and deep-research when the user opts in for higher-risk or volatile domains.
Builds evidence-ready artifacts: Produces a requirements-spec artifact (without writing it as durable documentation until the approval gate is answered) and hands off to planning once ready.

Quick Start

Use the brainstorming skill when you need to turn a vague feature request into a plan-ready requirements spec, then ask your AI tool to run: /supervibe-brainstorm.

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 idea into an approved requirements spec?▼

To turn a vague idea into an approved requirements spec, you need structured brainstorming that clarifies intent, defines MVP boundaries, sets non-goals, and establishes kill criteria before any coding begins.

What is the best way to scope an MVP for a product feature?▼

The best way to scope an MVP is to use mvp-discovery brainstorming, which captures the actual problem behind the request and produces a PRD-ready requirements spec for downstream planning and handoff.

How do I prevent premature coding sessions when planning a new feature?▼

Prevent premature coding by applying decision gating and scope-safety framing during brainstorming, which forces explicit risk assessment and interactive documentation approval before implementation starts.

When should I use deep research versus quick-idea brainstorming for product planning?▼

Use quick-idea brainstorming for fast requirement shaping, and switch to deep-research mode for higher-risk or volatile domains that require rigorous evidence packet construction before planning.

How do I define kill criteria and non-goals for a feature requirements spec?▼

Define kill criteria and non-goals during brainstorming by framing potential risks and verification boundaries upfront, ensuring the final requirements spec includes explicit conditions to abandon the feature.

Does brainstorming for product planning require a formal approval gate?▼

Yes, effective product planning requires an interactive documentation approval gate to review the evidence packet and requirements spec, ensuring the idea is fully validated before handoff to the planning stage.