Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores intent and design before implementation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Brainstorming Ideas Into Designs
_Adapted from the MIT-licensed superpowers plugin by Jesse Vincent. See NOTICE.md._
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions in rounds of up to four at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
<HARD-GATE>
Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
</HARD-GATE>
## Anti-Pattern: "This Is Too Simple To Need A Design"
Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
## Checklist
You MUST complete these in order:
1. **Explore project context** — check files, docs, recent commits
…
The line at the top of this page pins the label git:20261102.7d75f08, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_rhyqh7dmc3n5sdcw
GET https://markdownregistry.com/api/v1/resolve?ref=andreymudri/fleetmates/brainstorming
GET https://markdownregistry.com/api/v1/blob/737f0dcaa7147e1bb74470e254b054a64246c9b00264be2cf9ebf0a5ab6f690f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
andreymudri/fleetmates · skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute inline in this session, with checkpoints - the non-fleet…
andreymudri/fleetmates · skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete and needs integrating - re-runs the gate to verify each phase, then decides how the…
andreymudri/fleetmates · skills/fleet-lifecycle/SKILL.md · Use when spawning, listing, messaging, scaling, stopping, or resuming background teammates on a run.
andreymudri/fleetmates · skills/fleet-supervision/SKILL.md · Use when checking what a running fleet is doing - renders the digest, surfaces blocked or failed teammates, and…
andreymudri/fleetmates · skills/grilling/SKILL.md · Use when a plan, spec or design still has unresolved decisions, when the user says "grill me" or asks to be…
andreymudri/fleetmates · skills/parallel-execution/SKILL.md · Use when executing a written plan across background teammates - splits it into phases, dispatches worktree-isolated…
andreymudri/fleetmates · skills/phase-gate/SKILL.md · Use when a phase finished and needs an automated verdict before integration - runs command, agent, and MCP checks and…
andreymudri/fleetmates · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions - requires technical verification rather than…
andreymudri/fleetmates · skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - reproduce and isolate…
andreymudri/fleetmates · skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code - write the failing test first and…
obra/superpowers · skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, modifying…
jetbrains/thinkrail · packages/pi-thinkrail-workflow/skills/brainstorming/SKILL.md · Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or…
foryourhealth111-pixel/vibe-skills · bundled/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
a5c-ai/babysitter · library/methodologies/superpowers/skills/brainstorming/SKILL.md · Use when starting any creative work - creating features, building components, adding functionality, or modifying…
a5c-ai/babysitter · library/methodologies/rpikit/skills/brainstorming/SKILL.md · Clarify vague requirements through exploratory questioning and option generation before committing to research or…
mohitagw15856/pm-claude-skills · exports/openclaw/brainstorming/SKILL.md · Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria —…
