CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-advanced-elicitation

Pushes a draft off its first answer with critique methods and proposes one revision. Use when the user or another skill names bmad-advanced-elicitation, or the user says "advanced elicitation". Not for a critique or a named method such as pre-mortem without that name.

Quality

87%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exceptionally tight, well-engineered instruction skill: every section carries executable direction, the multi-round workflow is sequenced with acceptance gates and fallback paths, and the method catalog is kept out of context behind a purpose-built lookup script. The only noticeable gap is the absence of a single worked example (a brief, a return, a report section) to anchor the formats it specifies so precisely.

DimensionReasoningScore

Conciseness

The body is telegraphic instruction with zero padding: concepts like "expert panel, stakeholder lens, Delphi" and cold readers are referenced without explanation, and every sentence directs an action or a format (e.g. "Save each return as `round-<r>-push-<n>-<method>.md`... the open push as `open`"). It assumes Claude's competence throughout; not 4 because there is no over-explanation anywhere to trim.

5 / 5

Actionability

Guidance is highly executable: exact uv-run command pipelines, a fully enumerated five-part brief spec, a precise return shape ("the form as the body, then a `## Findings` list... at most five findings"), exact file-naming conventions, and an enumerated user-choice list. It falls just short of 5 because no worked example of a brief, return, or report section is provided, and what a finding's "location" looks like is left unspecified — the anchor-5 criteria ask for specific examples covering the common cases; it is well above 3 since nothing is pseudocode or vague.

4 / 5

Workflow Clarity

The workflow is explicitly sequenced (Setup → Target/Start → Brief → Round → Merge → Present and Choose → Done) with checkpoints throughout: "Stop to ask first only when there is no clear target", "Nothing in the target changes until the user accepts", error-recovery loops ("Script not found means BMad is not set up here: offer the bmad skill's setup... then run it again"; the without-subagents fallback), and a per-change applied/rejected record under each round. This matches the anchor for clear sequence with explicit validation and feedback loops; not 4 because no checkpoint category is missing.

5 / 5

Progressive Disclosure

The bulk content — the 9KB method catalog in assets/methods.csv — is deliberately kept out of context and served in lean slices through the verified bundle script scripts/pick_methods.py (`list`, `show`, `random`, with `--all` gated as deliberate), and the SKILL.md body references only that script plus ecosystem setup scripts, all one level deep. Clear overview, appropriately split content, easy navigation; not 4 because the split and the serving commands are both explicit and verified against the actual bundle.

5 / 5

Total

19

/

20

Passed

Description

75%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 is well-structured: third-person voice, an explicit what, an explicit when with concrete trigger phrases, and a negative scope clause that sharply limits conflict risk. Its main weakness is discoverability — the trigger vocabulary is essentially the skill's own name, with few natural phrases a user would say when they want draft-challenging but do not know the skill exists.

Suggestions

Add one or two natural trigger phrases users would say without knowing the skill's name (e.g. 'push back on this draft', 'pressure-test this plan') to the 'Use when' clause.

Name a concrete critique mechanism or two (e.g. 'cold readers', 'edge-case sweeps') in the what-clause so the capability is specific rather than covered by the generic phrase 'critique methods'.

DimensionReasoningScore

Specificity

"Pushes a draft off its first answer with critique methods and proposes one revision" names the domain and exactly two concrete actions, matching the anchor for 1-2 concrete actions but not comprehensive coverage. It is not 4 because fewer than several specific actions are listed and "critique methods" names no actual method; it is not 2 because the two actions stated are concrete, not minimal or generic.

3 / 5

Completeness

It explicitly answers both what ("Pushes a draft off its first answer with critique methods and proposes one revision") and when ("Use when the user or another skill names bmad-advanced-elicitation, or the user says 'advanced elicitation'") with concrete trigger phrases, plus an explicit not-for clause. This clearly matches the top anchor; a 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Relevant keywords are present ("advanced elicitation", "bmad-advanced-elicitation", "pre-mortem", "critique"), but triggering relies almost entirely on the user naming the skill, so common natural variations a user would say without knowing the name (e.g. "challenge this draft", "pressure-test this plan") are missing. It is not 2 because the terms present are specific rather than generic, and not 4 because the natural-phrase coverage outside the skill's own name is thin.

3 / 5

Distinctiveness Conflict Risk

"Not for a critique or a named method such as pre-mortem without that name" explicitly disambiguates the nearest conflicting use cases, and the name-gated triggers ("names bmad-advanced-elicitation", "says 'advanced elicitation'") make accidental triggering very unlikely — a clear niche with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/core-tools/bmad-advanced-elicitation/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.