super-brainstorm

Name: super-brainstorm
Availability: InStock
Author: brunolimaff-jpg

Convert feature ideas into validated design specifications before implementation.

Updated Feb 19, 2026

Search Tags:#design #planning #architecture #requirements #spec writing #interviewing #codebase-first

Ready to run

npx skills add https://github.com/brunolimaff-jpg/NOVO-APP --skill super-brainstorm-brunolimaff-jpg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: super-brainstorm
Source: https://github.com/brunolimaff-jpg/NOVO-APP/tree/main/.agents/skills/archive/2026-04-curation/super-brainstorm
Command: npx skills add https://github.com/brunolimaff-jpg/NOVO-APP --skill super-brainstorm-brunolimaff-jpg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents costly rework by converting vague feature requests and architectural uncertainty into a validated, user-approved design spec before implementation starts.

Core Features & Use Cases

Plan-mode design interview: Deep-scans existing docs and codebase, then runs a relentless, structured question flow to resolve requirements and constraints.
Spec-first hard gates: Enforces plan-mode and blocks any implementation, code changes, or scaffolding until the design is fully approved.
Design spec output + review loop: Writes the approved spec to docs/plans and includes an internal review loop to catch gaps before proceeding.

Quick Start

Use super-brainstorm to design your next feature by running it in response to the request "Brainstorm the system design and produce an implementation-ready spec."

Frequently Asked Questions about super-brainstorm

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

FAQPage Schema

How do I turn vague feature ideas into validated design specs before implementation?▼

To turn vague feature ideas into validated design specs, run a structured plan-mode interview that scans your codebase and docs to resolve requirements, then outputs an approved specification to your repository plans path.

What's the best way to plan architectural decisions without starting implementation too early?▼

The best way to plan architectural decisions safely is by enforcing spec-first hard gates that block code changes and scaffolding until a multi-branch requirements discovery interview is fully approved.

How does a codebase-first design interview work for refactoring and system changes?▼

A codebase-first design interview works by performing deep reconnaissance on existing documentation and source code, then conducting a relentless linear question flow to resolve constraints before writing a design spec.

Can I write implementation-ready specifications for new features directly to my docs path?▼

Yes, you can write implementation-ready specifications directly to the docs/plans directory after completing an internal review loop to catch gaps before proceeding with the feature design.

Does this approach support multi-branch requirements discovery for component design?▼

Yes, this approach supports multi-branch requirements discovery by applying structured questioning to component design and system changes, ensuring all architectural constraints are resolved before spec approval.

Why should I use a spec-first workflow instead of immediately scaffolding new features?▼

You should use a spec-first workflow to prevent costly rework, because it converts architectural uncertainty and vague requests into an approved design specification before any implementation work begins.