Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

brainstorm

Structured exploration before coding — one question at a time

Ejecutar en Manus

Resumen

Structured exploration before coding — one question at a time

Comando de instalación

npx skills add https://github.com/Vincent-20-100/metadev-protocol --skill brainstorm

Copia y pega este comando en Claude Code para instalar la habilidad

Fuente

Vincent-20-100/metadev-protocol

Estrellas1

Forks0

Actualizado12 de abril de 2026, 11:23

SKILL.md

readonly

name	brainstorm
description	Structured exploration before coding — one question at a time

If you have the Superpowers plugin installed, prefer superpowers:brainstorming for a more thorough design process. This skill is a lightweight fallback.

You are in BRAINSTORM mode. Your job is to explore the idea, not implement it.

Hard rules

Ask ONE question at a time
For each decision, propose 2-3 alternatives with trade-offs and your recommendation
Apply YAGNI aggressively — cut scope creep
DO NOT write any code, create any file, or make any edit
When the exploration is complete, write the summary to .meta/scratch/brainstorm.md

Process

Understand the goal — ask what, why, for whom
Explore constraints — what's non-negotiable, what's flexible
For each design decision, present options with your recommendation
Validate the full picture with the user
Write brainstorm.md with: decisions taken, alternatives rejected (with reasons), open questions

Verification

Before finishing, confirm:

At least 2 alternatives were considered for each major decision
YAGNI was applied — no speculative features survived
Open questions are listed (not swept under the rug)
Brainstorm file is written to .meta/scratch/

Rationalizations (why you must NOT skip steps)

Excuse	Why it's wrong
"I already know the best approach"	If you haven't considered alternatives, you don't know it's the best. You know it's the first.
"This is too simple to brainstorm"	Simple problems with wrong assumptions become complex problems later.
"The user seems to know what they want"	Explore anyway. Users often discover what they actually want during brainstorm.
"Let me just ask a few questions and start coding"	Brainstorm produces a written artifact. Questions in chat disappear from context.

Output format

Write to .meta/scratch/brainstorm.md:

# Brainstorm — [topic]

**Date:** [date]

## Decisions

- **[Decision 1]:** [choice] — because [reason]. Rejected: [alternative] ([why])
- ...

## Open questions

- ...

## Next step

Run /plan to break this into tasks.

Más de este repositorio

mismo repositorio

save-progress

Vincent-20-100/metadev-protocol

Pre-commit checklist + context update — runs deterministic checks, updates PILOT.md and SESSION-CONTEXT.md. Does NOT commit.

2026-04-211

research

Vincent-20-100/metadev-protocol

External research with WebSearch + WebFetch + MCP — structured output to .meta/references/raw/

2026-04-151

tech-watch

Vincent-20-100/metadev-protocol

Unified tech-watch skill — sweep mode (automated fetch of emerging repos/articles near project themes) and deep mode (structural analysis of one specific GitHub repo). Fuses /radar (sweep) and /audit-repo (deep) with a shared card schema in .meta/references/research/.

2026-04-151

research

Vincent-20-100/metadev-protocol

External research with WebSearch + WebFetch + MCP — structured output to .meta/references/raw/

2026-04-151

vision

Vincent-20-100/metadev-protocol

Fill or update the Vision section in PILOT.md — problem / target user / V1 scope / north star metric

2026-04-131

plan

Vincent-20-100/metadev-protocol

Break work into concrete tasks with verification steps

2026-04-121

Fuente

Vincent-20-100

Vincent-20-100/metadev-protocol

Abrir repositorio de GitHub Ver repositorios del creador

Comando de instalación

Descarga

Ejecutar en Manus

Útil paraSOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras13-1082L4

name	brainstorm
description	Structured exploration before coding — one question at a time

If you have the Superpowers plugin installed, prefer superpowers:brainstorming for a more thorough design process. This skill is a lightweight fallback.

You are in BRAINSTORM mode. Your job is to explore the idea, not implement it.

Hard rules

Ask ONE question at a time
For each decision, propose 2-3 alternatives with trade-offs and your recommendation
Apply YAGNI aggressively — cut scope creep
DO NOT write any code, create any file, or make any edit
When the exploration is complete, write the summary to .meta/scratch/brainstorm.md

Process

Understand the goal — ask what, why, for whom
Explore constraints — what's non-negotiable, what's flexible
For each design decision, present options with your recommendation
Validate the full picture with the user
Write brainstorm.md with: decisions taken, alternatives rejected (with reasons), open questions

Verification

Before finishing, confirm:

At least 2 alternatives were considered for each major decision
YAGNI was applied — no speculative features survived
Open questions are listed (not swept under the rug)
Brainstorm file is written to .meta/scratch/

Rationalizations (why you must NOT skip steps)

Excuse	Why it's wrong
"I already know the best approach"	If you haven't considered alternatives, you don't know it's the best. You know it's the first.
"This is too simple to brainstorm"	Simple problems with wrong assumptions become complex problems later.
"The user seems to know what they want"	Explore anyway. Users often discover what they actually want during brainstorm.
"Let me just ask a few questions and start coding"	Brainstorm produces a written artifact. Questions in chat disappear from context.

Output format

Write to .meta/scratch/brainstorm.md:

# Brainstorm — [topic]

**Date:** [date]

## Decisions

- **[Decision 1]:** [choice] — because [reason]. Rejected: [alternative] ([why])
- ...

## Open questions

- ...

## Next step

Run /plan to break this into tasks.