m3taz-ahmed/aizee / skills/bmad-advanced-elicitation
bmad-advanced-elicitation
VerifiedPushes 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| assets/methods.csv | other | 8.9 KB |
| bmod.toml | config | 122 B |
| customize.toml | config | 3.4 KB |
| evals/cases.json | config | 6.1 KB |
| evals/files/pantry-pal.md | markdown | 1.2 KB |
| evals/files/prd-notifications.md | markdown | 3.2 KB |
| evals/files/rollout-plan.md | markdown | 1.3 KB |
| evals/triggers.json | config | 3.1 KB |
| scripts/pick_methods.py | script | 16.1 KB |
| scripts/tests/test_pick_methods.py | script | 14.5 KB |
customize.toml
View on GitHub# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for bmad-advanced-elicitation.
#
# Override files (not edited here):
# {project-root}/_bmad/custom/bmad-advanced-elicitation.toml (team)
# {project-root}/_bmad/custom/bmad-advanced-elicitation.user.toml (personal)
[workflow]
# --- Configurable below. Overrides merge per BMad structural rules: ---
# scalars: override wins • plain arrays: append
# arrays of tables keyed by `code`: matching key replaces, new keys append
# The method catalog served by `uv run {skill-root}/scripts/pick_methods.py`. Columns:
# num, direction, method_name, description, form, tier, aliases.
# direction: wrong | missing | premise | simplify | future | other-side
# (find what is wrong, find what is missing, challenge the premise,
# simplify or re-pitch, stress against the future, argue the other side)
# form: one line saying what the method's output looks like; quoted into the brief
# tier: core (recommended) | more (kept so a method asked for by name resolves)
# aliases: earlier names of the method, separated by semicolons; optional
# Swap the path in team/user TOML to ship a different catalog. Use `{skill-root}`,
# `{project-root}` or an absolute path; a relative path resolves from the
# working directory.
methods_file = "{skill-root}/assets/methods.csv"
# Session output. The staged target, each push's return and the report land in
# `{output_dir}/{output_folder_name}/`; `{topic_slug}` is a kebab-case name for
# the target, filled at run time. The report is `{output_folder_name}.md`.
output_dir = "{output_folder}/{active_initiative}"
output_folder_name = "elicitation-{topic_slug}"
# Methods to run when the call names none, by method_name, shipped or from
# additional_methods, for example ["Pre-mortem Analysis", "Red Team"]. Empty: the
# skill chooses two or three against where the target looks weak. Team and user
# lists append, so both sets run.
default_methods = []
# Steps run before and after the shipped activation steps. Literal instructions;
# append-merges.
activation_steps_prepend = []
activation_steps_append = []
# Facts held for every session: methods or directions to favor or avoid, how
# pushback should land, house rules for applying changes. Literal sentences, or
# `file:` followed by a path or glob under {project-root} to read. Append-merges,
# so team and personal entries both apply.
#
# Examples (set in team/user override TOML):
# persistent_facts = [
# "Lead with a stress-against-the-future method for anything touching production.",
# "Never offer methods with several voices.",
# ]
persistent_facts = []
# Instructions run once the accepted version has been handed back.
on_complete = []
# Extra methods merged into the catalog without editing the shipped CSV. Add one
# when the team has a critique method of its own, or to retune a shipped one by
# reusing its method_name. Every entry needs a `code`, the merge key across
# override layers; `direction` takes one of the six keys above. The merge rules are in
# `uv run {skill-root}/scripts/pick_methods.py --help`.
#
# Example (set in team/user override TOML):
# [[workflow.additional_methods]]
# code = "regulatory-inversion"
# direction = "premise"
# method_name = "Regulatory Inversion"
# description = "Start from the compliance constraint and ask what it makes possible"
# form = "The constraint, the possibilities only it allows, and the design that uses them"
additional_methods = []
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |