void-brainstorm

Guides raw ideas through structured questioning into approved written specs before any code.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-brainstorm-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-brainstorm
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-brainstorm
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-brainstorm-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coding agents jump straight into implementation on half-formed ideas, producing fast code for the wrong problem. This Skill enforces a design-first discipline: it pressure-tests raw ideas, asks clarifying questions one at a time, proposes 2-3 approaches, and blocks all implementation until a spec is written to docs/specs/ and explicitly approved. ## Core Features & Use Cases - Hard gate on implementation: No code, scaffolding, or implementation skills may run until the spec is written, self-reviewed, and approved by the user. - Idea pressure-testing: A vendored diagnostic mode challenges raw product ideas with six forcing questions on demand reality, status quo, target user, and narrowest paid wedge. - Structured design process: One question at a time, multi-choice preferred, 2-3 approaches with trade-offs, section-by-section design approval, and a 10x ambition pass before settling scope. - Use Case: You say "I want to build a notification system for our app." The Skill asks clarifying questions, compares push vs. polling vs. hybrid architectures, writes the agreed design to docs/specs/2026-01-15-notifications.md, and only then hands off to the planning skill. ## Quick Start Ask the agent to help you think through and design a new feature idea before writing any code, and it will interview you, propose approaches, and produce an approved spec document.

Frequently Asked Questions about void-brainstorm

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

FAQPage Schema
How do I stop an AI coding agent from writing code before the design is agreed?

Use a hard-gate brainstorm process that blocks all implementation until a spec is written to docs/specs/ and explicitly approved. The agent asks clarifying questions, presents 2-3 approaches, and only transitions to planning after your sign-off.

How to validate a raw product idea before building it?

Run a pressure-testing diagnostic that asks six forcing questions one at a time: demand evidence, current workarounds, the specific user, the narrowest paid wedge, observed usage surprises, and future relevance. Weak or vague answers are challenged rather than accepted.

Does this design process apply to small or simple features?

Yes, the hard gate applies to every project regardless of perceived simplicity. Simple projects get short specs of a few sentences, but the spec must still be written, self-reviewed, and approved before implementation starts.

When should brainstorming not be triggered?

Skip it for bugs with one correct answer, mechanical refactors, naming choices local to one function, or preferences with no lasting consequence. The test is whether someone six months later would need to know why the decision was made.

What happens after the spec is approved?

The only allowed transition is to the planning skill, which turns the approved spec into an implementation plan. The spec also declares the TDD mode per phase and links to a tracker ticket once one is created.