Convert ambiguous feature ideas into an approved requirements spec for planning handoff.
npx skills add https://github.com/vTRKA/supervibe --skill brainstorming-vtrka
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
It prevents chaotic or premature coding sessions by transforming an ambiguous idea into an approved requirements spec before planning or implementation.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
sommioFacilitates collaborative brainstorming to draft a requirements document.
mliudevCreate an approved feature spec with acceptance criteria and a QA plan.
timzaakEvaluate feature readiness for the t-tools workflow and generate a Markdown decision brief.
lukeyliasConvert resolved product discussions into a structured PRD document.
