Brainstorming
Production ready. AI Agent Workflow System for Claude Code
npx -y skills add ngocsangyem/MeowKit --skill brainstormingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate or compare multiple technical approaches for one validated decision. Do not use for product discovery or an existing plan.
SKILL.md
3.7 KB, as published. Nobody here has run it
Brainstorming
Use for generating or comparing multiple technical approaches to one validated decision.
Boundary: mk:office-hours answers “should we build this?”; this skill answers “how should we build it?” A bare “brainstorm” request is ambiguous: ask whether the user wants product discovery/validation or technical approaches. Do not route from that word alone.
Profiles
- quick /
--depth quick(default) — restate the decision in one line; give 2-4 technically distinct options and one recommendation. If a material fact is missing, state the assumption rather than running discovery. Return inline and stop. Do not load techniques, scout, scoring, challenge, reports, plans, wiki candidates, memory, or handoff. - deep /
--depth deep— load the needed technique and use the deep workflow below. A report, HTML output, or handoff is optional and only produced when requested or needed by an active plan.
Routing
| Situation | Route |
|---|---|
| New product, feature, or side-project value is unvalidated | mk:office-hours |
| Observed failure or root-cause work | mk:investigate |
| Existing plan, verdict, or brainstorm needs critique | mk:plan-ceo-review or mk:elicit |
| Generic Q&A or a single implementation detail | answer directly or use mk:docs-finder |
Defaults
Use at least two alternatives. Quick returns 2-4; deep generates 3-8 and never more than 8. Keep multiple dimensions in one run when they serve one decision or report; split only 3+ independently shippable concerns.
Quick Workflow
- Restate the validated decision and any material assumption.
- Give 2-4 technically distinct options with the key trade-off for each.
- Recommend one option and return inline. Do not create a report, plan, wiki candidate, or memory entry.
Deep Workflow
- Confirm the decision, binding constraint, success criterion, and excluded scope. Ask at most three focused questions when needed.
- If 3+ independently shippable concerns are bundled, ask to choose one. Use a compact scout summary only when current codebase touchpoints change the decision.
- Load one technique from
references/techniques/; generate 3-8 technical approaches without scoring while generating. - Run one anti-bias pivot, then the challenge pass in
references/challenge-pass.mdbefore recommending. - Load scoring only for deep scoring. Write a report, HTML output, or handoff only when requested or needed by an active plan. For a requested report, an optional
mewkit wiki handoff suggestfollows.claude/skills/wiki/references/terminal-handoff-advisory.md; it is fail-open and never runs for quick.
References
references/context-budget.md— deep clarification, count, pivot, and challenge limitsreferences/techniques/— choose one technique for a deep runreferences/challenge-pass.mdandreferences/scoring-criteria.md— deep convergence onlyreferences/editorial-html.md— HTML only for a requested report