brainstorming

Guides collaborative design dialogue to produce testable requirement specifications before implementation.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill brainstorming-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/brainstorming
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill brainstorming-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams often jump straight into coding without clarifying intent, requirements, or design, leading to rework and misaligned features. This Skill enforces a structured brainstorming workflow that turns rough ideas into approved, testable specification documents before any implementation begins. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents the design in sections for user approval. - Formal Spec Generation: Writes requirement documents using a REQ-NNN format with measurable acceptance criteria, test cases, NFR tables, and a test coverage matrix, saved to .ai/<topic>/specs/. - Quality Gates: Runs a mechanical pre-lint script and a spec-quality-gate review to catch placeholders, vague language, and untestable requirements before planning. - Visual Companion: Optional browser-based companion server for showing mockups, diagrams, and layout comparisons during visual design questions. - Use Case: Before building a new feature, invoke the skill to capture requirements, produce a reviewed spec, and hand off cleanly to architecture or implementation planning. ## Quick Start Ask the AI to brainstorm the design for your new feature before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I write a software specification before coding?

Use a structured brainstorming workflow: explore project context, ask clarifying questions one at a time, propose 2-3 approaches with trade-offs, then write a spec with REQ-NNN requirements, measurable acceptance criteria, and test cases per requirement.

What makes a requirement testable in a design spec?

A testable requirement is binary or measurable, with numbers, thresholds, or deterministic conditions rather than vague words like fast or intuitive. Each acceptance criterion needs a test case that would fail if the implementation were subtly wrong.

When should brainstorming happen in a development workflow?

Brainstorming should happen before any implementation, after business context is captured. The skill enforces a hard gate: no code, scaffolding, or implementation skills run until a design is presented and the user approves it.

Does the brainstorming skill work for small changes or bug fixes?

Yes, every project goes through the process, but the design can be a few sentences for simple changes. Bug fixes and config changes skip the business context gate and can proceed directly to plan writing after approval.

What is the visual companion in the brainstorming skill?

The visual companion is an optional local browser server that displays mockups, diagrams, and layout options during design questions. It is offered once for consent and used per-question only when content is genuinely visual rather than textual.