bmad-advanced-elicitation
Skill17 starsChanged 4 months 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.
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
DO NOT skip steps or change the sequence
- Distinctive: line 25
When invoked from another prompt or process:
- Very specific: line 94
CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.
- Distinctive: line 95
CRITICAL: ONLY if Yes, apply the changes.
- Distinctive: line 101
When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being potentially …
- Distinctive: line 114
After selection, execute the method as described in the Case 1-5 above
- Distinctive: line 128
Method execution: Use the description from CSV to understand and apply each method
- Distinctive: line 129
Output pattern: Use the pattern as a flexible guide (e.g., "paths -> evaluation -> selection")
- Distinctive: line 135
Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution
“Common” is measured: kept by at least 6 in 10 of the 16 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
Goal: Push the LLM to reconsider, refine, and improve its recent output.
CRITICAL LLM INSTRUCTIONS
- MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
- DO NOT skip steps or change the sequence
- HALT immediately when halt-conditions are met
- Each action within a step is a REQUIRED action to complete that step
- Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the
communication_language
INTEGRATION (When Invoked Indirectly)
When invoked from another prompt or process:
- Receive or review the current section content that was just generated
- Apply elicitation methods iteratively to enhance that specific content
- Return the enhanced version back when user selects 'x' to proceed and return back
- The enhanced content replaces the original section content in the output document
FLOW
Step 1: Method Registry Loading
Action: Load ./methods.csv for elicitation methods. If party-mode may participate, resolve the agent roster via:
python3 {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key agentsThe resolver merges four layers in order: _bmad/config.toml (installer base, team-scoped), _bmad/config.user.toml (installer base, user-scoped), _bmad/custom/config.toml (team overrides), and _bmad/custom/config.user.toml (personal overrides). Each entry under agents is keyed by the agent's code and carries name, title, icon, description, module, and team.
CSV Structure
- category: Method grouping (core, structural, risk, etc.)
- method_name: Display name for the method
- description: Rich explanation of what the method does, when to use it, and why it's valuable
- output_pattern: Flexible flow guide using arrows (e.g., "analysis -> insights -> action")
Context Analysis
- Use conversation history
- Analyze: content type, complexity, stakeholder needs, risk level, and creative potential
Smart Selection
- Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential
- Parse descriptions: Understand each method's purpose from the rich descriptions in CSV
- Select 5 methods: Choose methods that best match the context based on their descriptions
- Balance approach: Include mix of foundational and specialized techniques as appropriate
Step 2: Present Options and Handle Responses
Display Format
**Advanced Elicitation Options**
_If party mode is active, agents will join in._
Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
1. [Method Name]
2. [Method Name]
3. [Method Name]
4. [Method Name]
5. [Method Name]
r. Reshuffle the list with 5 new options
a. List all methods with descriptions
x. Proceed / No Further ActionsResponse Handling
Case 1-5 (User selects a numbered method):
- Execute the selected method using its description from the CSV
- Adapt the method's complexity and output format based on the current context
- Apply the method creatively to the current section content being enhanced
- Display the enhanced version showing what the method revealed or improved
- CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.
- CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to follow the instructions given by the user.
- CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations
Case r (Reshuffle):
- Select 5 random methods from methods.csv, present new list with same prompt format
- When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being potentially the most useful for the document or section being discovered
Case x (Proceed):
- Complete elicitation and proceed
- Return the fully enhanced content back to the invoking skill
- The enhanced content becomes the final version for that section
- Signal completion back to the invoking skill to continue with next section
Case a (List All):
- List all methods with their descriptions from the CSV in a compact table
- Allow user to select any method by name or number from the full list
- After selection, execute the method as described in the Case 1-5 above
Case: Direct Feedback:
- Apply changes to current section content and re-present choices
Case: Multiple Numbers:
- Execute methods in sequence on the content, then re-offer choices
Step 3: Execution Guidelines
- Method execution: Use the description from CSV to understand and apply each method
- Output pattern: Use the pattern as a flexible guide (e.g., "paths -> evaluation -> selection")
- Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)
- Creative application: Interpret methods flexibly based on context while maintaining pattern consistency
- Focus on actionable insights
- Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user indicates otherwise)
- Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory already
- Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution
- Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session
- Each method application builds upon previous enhancements
- Content preservation: Track all enhancements made during elicitation
- Iterative enhancement: Each selected method (1-5) should:
- Apply to the current enhanced version of the content
- Show the improvements made
- Return to the prompt for additional elicitations or completion
Other versions24 projects use a version of this.
Word for word · 8
- delorenj/mcp-server-trello★ 446100% same
- mugsun/curdx-flow★ 4100% same
- jeffrey2423/commit-like-pro★ 2100% same
- PaulKnauer/sonos-mcp-server★ 1100% same
- Tyler-Hughes312/mycelium★ 1100% same
- Wellington-HMV/agentiq★ 1100% same
- areesh-ali/AMKP★ 0100% same
- GauravRatnawat/claude-cost-optimizer★ 0100% same
Edited · 12
- paulpreibisch/AgentVibes★ 15598% same
- laraxot/laravelpizza.com★ 2667% same
- 2233admin/opencli-Razormind★ 1813% same
- DogaOztuzun/branchdeck★ 1897% same
- armelhbobdad/oh-my-skills★ 798% same
- MysterionRise/forgetest★ 413% same
- salacoste/oh-my-bmad★ 298% same
- AvishkaGihan/ventureiq★ 198% same
- ChrisBP-Dev/portfolio★ 167% same
- cwoodcox/on-record★ 097% same
2 more not listed
Wrote their own version · 4
- bmad-code-org/BMAD-METHOD★ 55ksame name
- alvin-reyes/better-agentic-ide★ 85same name
- delorenj/skills★ 16same name
- mannnrachman/pi-bmad★ 2same name
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.
Used alongsideProjects with it also use bmad-dev-auto, bmad-editorial-review and 1 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.
PaulKnauerSkillbmad-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 5 projects that use this
2233adminSkillbmad-review-verification-gap
Deprecated — forwards to bmad-review.
Also in 5 projects that use this
In this repository113 other files it gives its agents.
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-tech-writerSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-brainstormingSkill
- bmad-check-implementation-readinessSkill
- bmad-checkpoint-previewSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-index-docsSkill
- bmad-investigateSkill
- bmad-market-researchSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- bmad-shard-docSkill
- bmad-specSkill
- bmad-sprint-planningSkill
- bmad-sprint-statusSkill
- bmad-teach-me-testingSkill
- bmad-teaSkill
- bmad-technical-researchSkill
- bmad-testarch-atddSkill
- bmad-testarch-automateSkill
- bmad-testarch-ciSkill
- bmad-testarch-frameworkSkill
- bmad-testarch-nfrSkill
- bmad-testarch-test-designSkill
- bmad-testarch-test-reviewSkill
- bmad-testarch-traceSkill
- bmad-uxSkill
- bmad-v6-story-pipelineSkill
- bmad-validate-prdSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- The first 60 shown.
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.

