bmad-walkthrough
Skill1 starsChanged 16 days agoApache-2.0View on GitHub
Walk the user through reviewing a change: what it is for, what to look at closely, and how to test it. Use when the user says "walkthrough", "walk me through this change", or "human review"
5 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- bmad-code-org/BMAD-METHODtheir own version, first seen Nov 15, 2026
- delorenj/skillsword for word, first seen Nov 7, 2026
- alvin-reyes/better-agentic-idetheir own version, first seen Oct 17, 2026
- salacoste/oh-my-bmadedited, first seen Sep 13, 2026
- mannnrachman/pi-bmadedited, first seen Sep 8, 2026
Other versions5 projects use a version of this.
Word for word · 1
- delorenj/skills★ 17100% same
Edited · 2
- mannnrachman/pi-bmad★ 296% same
- salacoste/oh-my-bmad★ 297% same
Wrote their own version · 2
- bmad-code-org/BMAD-METHOD★ 55ksame name
- alvin-reyes/better-agentic-ide★ 43same 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.
In this repository157 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-builderSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-bmb-setupSkill
- bmad-brainstormingSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-checkpoint-previewSkill
- bmad-cis-agent-brainstorming-coachSkill
- bmad-cis-agent-creative-problem-solverSkill
- bmad-cis-agent-design-thinking-coachSkill
- bmad-cis-agent-innovation-strategistSkill
- bmad-cis-agent-presentation-masterSkill
- bmad-cis-agent-storytellerSkill
- bmad-cis-design-thinkingSkill
- bmad-cis-innovation-strategySkill
- bmad-cis-problem-solvingSkill
- bmad-cis-storytellingSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-dev-autoSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-reviewSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-eval-runnerSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-loop-resolveSkill
- bmad-loop-setupSkill
- bmad-loop-sweepSkill
- bmad-market-researchSkill
- bmad-module-builderSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run.
- Very specific: line 43
Run uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} and resolve:
- Very specific: line 68
Read fully and follow ./step-01-orientation.md to begin.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Walkthrough Workflow
Goal: Guide a human through reviewing a change — from purpose and context into details.
Your Role: You are assisting the user in reviewing a change.
Conventions
- Bare paths (e.g.
step-01-orientation.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.
On Activation
Step 1: Resolve the Workflow Block
Run: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.
Step 4: Load Config
Run uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} and resolve:
implementation_artifactsplanning_artifactscommunication_languagedocument_output_language
Step 5: Greet the User
Greet the user, speaking in {communication_language}.
Step 6: Execute Append Steps
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
Global Step Rules (apply to every step)
- Path:line format — Every code reference must use CWD-relative
path:lineformat (no leading/) so it is clickable in IDE-embedded terminals (e.g.,src/auth/middleware.ts:42). - Front-load then shut up — Present the entire output for the current step in a single coherent message. Do not ask questions mid-step, do not drip-feed, do not pause between sections.
- Language — Speak in
{communication_language}. Write any file output in{document_output_language}.
FIRST STEP
Read fully and follow ./step-01-orientation.md to begin.
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.

