bmad-advanced-elicitation
Skill43 starsChanged 32 days agoMITView on GitHub
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team
26 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- Brumm-Labs/kb-agentstheir own version, first seen Nov 16, 2026
- bmad-code-org/BMAD-METHODtheir own version, first seen Nov 15, 2026
- muslim-sec/skillstheir own version, first seen Nov 15, 2026
- snovak7/bmad-github-zoho-pipelineedited, first seen Nov 14, 2026
- armelhbobdad/oh-my-skillstheir own version, first seen Nov 9, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
Used with
Projects with it also use bmad-checkpoint-preview, bmad-dev-auto and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GauravRatnawatSkillbmad-checkpoint-preview
LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".
Also in 16 projects that use this
areesh-aliSkillbmad-dev-auto
One iteration of an unattended development loop. Use when invoked by name.
Also in 8 projects that use this
2233adminSkillbmad-editorial-review
Deprecated — forwards to bmad-review.
Also in 6 projects that use this
2233adminSkillbmad-review-verification-gap
Deprecated — forwards to bmad-review.
Also in 6 projects that use this
GauravRatnawatSkillbmad-investigate
Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.
Also in 5 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- laraxot/laravelpizza.com★ 2667% same
- 2233admin/opencli-Razormind★ 1972% same
- delorenj/skills★ 1791% same
- MysterionRise/forgetest★ 472% same
- mannnrachman/pi-bmad★ 291% same
- salacoste/oh-my-bmad★ 291% same
- ChrisBP-Dev/portfolio★ 167% same
- PaulKnauer/sonos-mcp-server★ 191% same
- snovak7/bmad-github-zoho-pipeline★ 072% same
Wrote their own version · 17
- bmad-code-org/BMAD-METHOD★ 55ksame name
- delorenj/mcp-server-trello★ 446same name
- paulpreibisch/AgentVibes★ 155same name
- DogaOztuzun/branchdeck★ 18same name
- marlonvidal/tech-manager-os★ 17same name
- armelhbobdad/oh-my-skills★ 7same name
- mugsun/curdx-flow★ 4same name
- jeffrey2423/commit-like-pro★ 2same name
- AvishkaGihan/ventureiq★ 1same name
- Brumm-Labs/kb-agents★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-brainstormingSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-evalSkill
- bmad-forge-ideaSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-retrospectiveSkill
- bmad-reviewSkill
- bmadSkill
- bmad-specSkill
- bmad-ticketSkill
- bmad-toolsmithSkill
- bmad-uxSkill
- bmad-walkthroughSkill
- bmod-core-toolsSkill
- bmod-methodSkill
- bmod-toolsmithSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
If {workflow.additional_methods} is non-empty, add --extra '<its entries as a JSON array>' (or a path to a JSON file holding them) on every …
- Distinctive: line 50
If the user picks methods: run them (several: in sequence), then offer the menu again.
- Distinctive: line 51
If the user chooses Reshuffle: reshuffle as above and offer the menu again.
- Very specific: line 52
If the user chooses List all: show the full catalog (list --all) as a compact table.
- Distinctive: line 64
Never change the work unless the user accepts the proposal.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Advanced Elicitation
You are BMad's shared refinement checkpoint: other skills invoke you at natural pauses to pressure the piece of work they just produced, and users call you directly on anything recent. The target is the most recent output in the conversation — a section, plan, draft, or decision — unless the caller or user points at something else. You offer a short menu of elicitation methods, run the chosen ones against the target, and hand back the improved version so the invoking flow resumes exactly where it paused. Work in the surrounding session's communication language.
Conventions
- Bare paths (e.g.
assets/methods.csv) resolve from{skill-root}(wherecustomize.tomllives);{project-root}-prefixed paths from the project working directory. {workflow.<name>}resolves to fields in the mergedcustomize.toml[workflow]table.
On Activation
- Resolve customization:
node {project-root}/_bmad/ade-runtime.mjs resolve_customization --skill {skill-root} --project-root {project-root} --key workflow.- Script not found: BMad is not set up here. Offer to run the
bmadskill's setup, installingbmadfirst if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again. - Any other failure: read
{skill-root}/customize.tomldirectly and use defaults.
- Script not found: BMad is not set up here. Offer to run the
- Hold every
{workflow.preferences}entry for the whole session, fix the target, and serve the first menu.
Serving the Catalog
scripts/pick_methods.py serves the method catalog (num, category, method_name, description, output_pattern) so it never enters context whole — the one exception is listing the full catalog, when the user asked for all of it. Invoke as:
node {project-root}/_bmad/ade-runtime.mjs pick_methods --skill-root {skill-root} --file {workflow.methods_file} <command>If {workflow.additional_methods} is non-empty, add --extra '<its entries as a JSON array>' (or a path to a JSON file holding them) on every call, so custom methods are first-class in menus, reshuffles, and listings.
categories— category names + counts, the cheap map.list --category <cat> [--category <cat>]— the index for chosen categories;--alldumps the whole catalog, only when listing all.show <name-or-num> [...]— full rows by name or num.random -n 5 --spread [--exclude <name>]...— a category-diverse random draw.
First menu: run categories, pick the 2–4 categories that fit the target (risk before a launch, technical for code, collaboration when stakeholders compete, creative when the content is flat), list them, and hand-pick five methods that attack the target from different angles — honoring {workflow.preferences}. Reshuffle: random -n 5 --spread, excluding everything already offered.
The Menu
HALT and give the user a choice:
- The five offered methods, listed by name. The user may pick one or several.
- Reshuffle — replace the list with five new options.
- List all — show the full catalog with descriptions.
- Proceed — no further elicitation.
This menu is the interface other skills and their users rely on — keep its options and behavior stable. When party mode is active in the session, add _Party mode is active — agents will join in._ under the heading.
- If the user picks methods: run them (several: in sequence), then offer the menu again.
- If the user chooses Reshuffle: reshuffle as above and offer the menu again.
- If the user chooses List all: show the full catalog (
list --all) as a compact table; a pick by name or number runs like a method choice. - If the user chooses Proceed: done. The current enhanced version is final for this content: hand it back to the invoking skill as the replacement for what it had, and signal completion so it continues. If anything shown was never accepted, confirm what should carry over before returning.
- Any other reply is direction: apply it to the target and offer the menu again.
Running a Method
Use the method's description as its intent and its output_pattern as a flexible flow guide; scale depth to the target — a paragraph gets a light pass, an architecture decision gets the full treatment. Each application works on the current enhanced version, so refinements compound. Show what the method revealed and the changes it proposes, then HALT and give the user a choice:
- Apply — accept the proposed changes.
- Reject — drop the proposal entirely.
- Or give different direction.
Never change the work unless the user accepts the proposal. If they reject it, drop the proposal entirely. Any other reply is instruction to follow.
When a method casts personas (round tables, panels, debates), reuse party members already in the session if party mode is active; otherwise resolve installed agents on demand via node {project-root}/_bmad/ade-runtime.mjs roster --skill {skill-root} --project-root {project-root} (its agents table is keyed by agent code; each entry carries name, title, icon, persona). If neither yields a fit, invent named viewpoints suited to the content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

