brainstorm

Interviews users to stress-test ideas and records outcomes in issue tracker.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill brainstorm-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill brainstorm-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often commit to building features before the idea has been properly examined, leading to wasted effort and rework. This Skill runs a relentless structured interview about an idea, surfacing hidden assumptions and open questions before any code is written, without ever touching the repository. ## Core Features & Use Cases - Structured idea interview: Runs a grilling session on a topic, dispatching sub-agents to gather facts from the codebase while the user makes the decisions. - Safe by design: Never writes to the repo—no branches, commits, or ADR files; its only write surface is the issue tracker, and only with user approval. - Three landing options: Ends by asking whether the thinking goes nowhere, becomes a structured idea issue (Why, Destination, Decisions so far, Not yet specified, Out of scope), or feeds directly into a feature build. - Use Case: Before building a new notification system, run the brainstorm skill to explore edge cases and trade-offs, then publish the settled decisions and open questions as an idea issue for a later feature session. ## Quick Start Ask the AI to brainstorm the topic of adding real-time notifications to the application.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I validate a feature idea before writing code?

Run a structured brainstorm interview that grills the idea from every angle, separating facts (gathered from the codebase by sub-agents) from decisions (made by you). The session ends with a clear record of settled decisions and remaining open questions.

What is the difference between brainstorming and starting a feature?

Brainstorming thinks an idea through without building anything and never writes to the repo, while a feature workflow produces code. Brainstorm output can feed directly into a feature session, which then only grills the questions still left open.

Does the brainstorm skill modify my repository?

No. It never creates branches, commits, pushes, or writes ADR or glossary files. Its only write surface is the issue tracker, and it writes there only if you explicitly choose to publish the thinking as an idea issue.

What goes into an idea issue in the issue tracker?

An idea issue has exactly five sections: Why (the problem motivating the idea), Destination (the desired outcome), Decisions so far (settled points with reasoning), Not yet specified (open questions), and Out of scope (deliberate exclusions).

When should I not use a brainstorm interview?

Skip it when the decision is already settled and you are ready to build, or when the topic is casual discussion rather than a design question about the repo. In those cases, go straight to a feature workflow or a plain chat.