bmad-review

BMad Review

Review content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.

The lens set is whatever {workflow.lenses} resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.

Inputs

• content — what to review: a diff, branch, uncommitted changes, file, ticket (initiative, epic, story, spike, bug), or any document. Args: [path].
• lenses (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form skill:bmad-review lenses=<code>[,<code>...] (the form bmm's doc_standards uses). Default: every applicable lens (a full review).
• also_consider (optional) — areas to keep in mind alongside each lens's normal analysis.
• claims (optional) — the change's own narrative: the commit messages it covers, or whatever description of it the caller supplied. Goes to the edge-case lens alone.
• pre-resolved customization (optional) — [workflow] field values supplied by a forwarding caller. See Execution step 1.

Conventions

• Bare paths (e.g. references/lens-edge-case-hunter.md) resolve from {skill-root} — this skill's installed directory, where customize.toml lives. {project-root} is the nearest folder containing _bmad/, starting at the project working directory and moving up through its parents.
• {workflow.<name>} resolves to fields in customize.toml's [workflow] table (overrides win per BMad merge rules).
• In style_guide, review_guidance, and persistent_facts, a value prefixed file: is a path or glob — load that file's contents. If a file: value cannot be read, name the failed file in the output header and continue: the shipped baseline for style_guide, the remaining entries otherwise.

Execution

1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow.

   • Script not found: BMad is not set up here. Offer to run the bmad skill's setup, installing bmad first 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.toml directly and use defaults.

   Forwarded activation: if a caller invoked you with pre-resolved customization fields (e.g. the bmad-editorial-review shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own customize.toml. Then execute each {workflow.activation_steps_prepend} entry in order, hold {workflow.persistent_facts} as standing context for the session, and treat {workflow.review_guidance} entries as standing review directives for every lens.

2. Load the content. Stage it once as a file: when the content is a branch, uncommitted work, or a commit range, use the repository's version-control tooling to write the unified diff to a uniquely-named file in the system temp directory and take that file's absolute path as the content. A branch means its diff against the merge base with its base branch; uncommitted work includes untracked files. Stage claims to its own file the same way — it is input for one lens, staged separately precisely so the other lenses never see it. If the content is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return [{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}] (no lens field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is code or docs; scope rules and lens applicability both depend on it. A document that defines behavior (a ticket, a plan, requirements) is docs that a behavioral lens may still apply to; judge by when.

3. Select lenses from {workflow.lenses}. A lens with an empty instruction is disabled. If the user or caller named lenses, run exactly those only — applies_to and when do not filter an explicit request. Otherwise run every enabled lens whose applies_to covers the content class (any always covers) and whose when applies.

4. Announce the plan in one line before running anything: the content class, the lenses about to run, and — when any lens has after set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each {workflow.activation_steps_append} entry in order.

5. Run the independent lenses — every selected lens without after. Each sees the content and also_consider, never another lens's findings. Follow each lens's instruction; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, launch every independent lens before handling any lens's result. Try running them simultaneously: spawn one per lens; give it the lens instruction with {skill-root} and paths resolved absolute, the absolute path of the staged content file (a lens prompt carries the path and the lens reads the file, never the content bytes; inline the content only when it was never staged as a file), any also_consider areas, the standing review directives, the claims path to the edge-case lens alone (marked to leave unread until its instructions call for it), and the constraint "Return ONLY your findings — no other output. Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer." Otherwise run the lenses sequentially yourself, completing one before starting the next.

6. Run the dependent lenses — every selected lens with after, once the lens it names has completed, passing that lens's findings in. A lens whose after target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other: launch every ready one before handling any of their results. Try running them simultaneously. When subagents are available, spawn them with the same constraint as independent lenses: "Return ONLY your findings — no other output. Do not invoke any skill, and do not spawn subagents of your own — you are the reviewer. Return your findings as text in your final message; do not route them through any findings-reporting tool the host may offer."

7. Assemble and present per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute {workflow.on_complete} if set.

Output

One JSON array holding every finding from every lens. Each finding carries:

• lens — the code of the lens that produced it
• location — where in the content (file:line-range for code, section for documents)
• trigger_condition — the problem, or the condition that exposes it, in one line
• guard_snippet — the concrete fix, guard, or missing check
• potential_consequence — what goes wrong if it ships as-is

Each lens file refines these semantics for its findings and may add lens-specific fields (e.g. kind/confidence on deletion findings, gap_shape/consumer/evidence on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. [] is valid when nothing is found. No severity, priority, or ranking anywhere.

Present per {workflow.output_format} — "json" (the raw array in a fenced json block), "markdown", or "both" — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per {workflow.output_preferences}.

When {workflow.report_path} is set, write the report there; otherwise present it in chat.