CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-brainstorming

Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/core-tools/bmad-brainstorming/SKILL.md

The canonical home for this skill is bmad-brainstorming in bmad-code-org/BMAD-METHOD

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong skill body: it is lean, assumes Claude's competence, and provides copy-paste-ready commands with explicit failure-handling branches. Its only weaknesses are mild — a few dense compound sentences that blur workflow checkpoints, and cross-section assembly required to piece together the full session flow. Progressive disclosure is exemplary, with every referenced bundle file present and clearly gated.

DimensionReasoningScore

Conciseness

The body is densely operational with essentially no padding — it never explains concepts Claude already knows, and lines like the numbered activation steps and memlog command specs carry maximum instruction per token. Not a 5 because a few phrases could still be trimmed (e.g. "The best sessions end with the user surprised by what came out" is flavor, and several long compound sentences could be split without losing content).

4 / 5

Actionability

Guidance is fully executable: exact commands with all flags (`uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic=...`), a regeneration command for the composer page, and even the exact message to send the user ("It should open in your browser — compose your session, click **Copy prompt**..."). Specific examples cover the common cases — pasted block, in-chat fallback, headless launch — with concrete parse rules for each.

5 / 5

Workflow Clarity

Sequencing is clear and well-structured: numbered activation steps with explicit failure branches (script not found → offer setup; no active_initiative → ask once), a session flow from Run a Session through Choosing Techniques, Converging, and Wrap-Up, and validation checkpoints like "confirm every entry ran" and "never claim it opened". Not a 5 because checkpoints occasionally require assembly across sections (memlog creation is defined in Framing but invoked in Run a Session; doc_workspace binding appears mid-section), and some edge handling (e.g. an unparseable pasted block) is left implicit.

4 / 5

Progressive Disclosure

The body is a genuine orchestrator overview that delegates detail through well-signaled, one-level-deep references — every cited file (references/mode-facilitator.md, mode-partner.md, mode-autonomous.md, headless.md, in-chat-techniques.md, converge.md, resume.md, finalize.md, assets/brain-selector.html, scripts/brain.py) exists in the bundle, and each is invoked with explicit load conditions ("load references/converge.md and follow it", "never load it otherwise"). Heavy content (the technique catalog) is correctly kept out of context behind brain.py commands, e.g. "Never pull the library whole into context".

5 / 5

Total

18

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly answers both 'what' and 'when' with explicit, natural trigger phrases, which is its main strength. However, the 'what' is thin (a single generic action clause) and trigger coverage stops at two phrases, leaving common variations unserved. It is solid but below the exemplar level of the rubric's good examples.

Suggestions

Expand the 'what' with 2-3 concrete capabilities, e.g. 'Facilitate a brainstorming session across facilitator, partner, or autonomous modes — selecting creative techniques, logging ideas to a session memory, and converging on the best ones.'

Broaden trigger coverage with natural variations users actually say: 'come up with ideas', 'generate ideas', 'let's brainstorm', 'I need ideas for...'.

State an artifact or outcome (e.g. a session memlog and a synthesized shortlist) to sharpen distinctiveness from generic ideation/planning skills.

DimensionReasoningScore

Specificity

"Facilitate a brainstorming session using diverse creative techniques" names the domain and one concrete action (facilitating a session), but "diverse creative techniques" is generic and the description omits what the skill actually does in a session (technique selection, convergence, synthesis, session resumption) — matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. Not a 2 because facilitating a brainstorming session is a genuine concrete action; not a 4 because no several specific actions are listed.

3 / 5

Completeness

Both halves are explicit: the 'what' is "Facilitate a brainstorming session using diverse creative techniques" and the 'when' is "Use when the user says 'help me brainstorm' or 'help me ideate'" with concrete quoted trigger phrases. Not a 5 because the 'what' is a single thin clause — unlike the 5-anchor example listing multiple concrete capabilities — so the description doesn't comprehensively state what the skill does.

4 / 5

Trigger Term Quality

The triggers "help me brainstorm" and "help me ideate" are natural phrases a user would say, but coverage stops at two: common variations like "come up with ideas", "generate ideas", "I need ideas for...", or "let's brainstorm" are absent — matching 'some relevant keywords but missing common variations or synonyms'. Not a 4 because the missing variations are numerous rather than 'a few'.

3 / 5

Distinctiveness Conflict Risk

The brainstorming/ideation niche with quoted 'help me brainstorm' triggers is clearly distinguishable and unlikely to fire for unrelated skills. Not a 5 because ideation overlaps with general planning, writing, or product-idea skills that could share the 'help me ideate' trigger; not a 3 because the trigger phrases are specific enough to avoid broad overlap.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

bmad-code-org/BMAD-METHOD

Path

skills/core-tools/bmad-brainstorming/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.