Menu

Individual skill

brainstorming

0upvotes

Use when the user wants to brainstorm, choose an approach, design something, or clarify an ambiguous or consequential change.

plugins/reidemeister94/development-skills/skills/brainstorming/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Brainstorming

Interview until you and the user share the same understanding.
Walk every branch of the decision tree and resolve dependent decisions in order.
Attach a recommended answer and its trade-off to every question.
Group only independent questions, as the [development loop](../../shared/development-loop.md) Reach agreement section requires.
The number of questions follows the ambiguity: stop when every branch is settled, not at a fixed count.
This rule applies on every path, whether or not the task needs a plan and chronicle.

<HARD-GATE>
Do not write code before the presented design or plan is approved.
Do not write the plan while purpose, scope, solved state, proof, or a contested design remains unresolved.
Once these points are settled, return them to the development loop.
The loop presents the complete design or plan before asking for approval.