Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a tight, highly executable activation procedure: exact commands, explicit placeholder-resolution conventions, sequenced steps with error-recovery branches, and a clean single-file structure with well-signaled on-demand external files. Its only weakness is mild density in a couple of packed sentences (Step 5 conventions, Step 8 dispatch) that could be broken up for readability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and procedural with no explanation of concepts Claude already knows, but a few passages — the packed Step 5 ticket-path conventions sentence ("tickets `initiative-*.md` (older projects `SPEC*.md`), `tickets/epic-*/epic-*.md`, and...") and parts of the Step 8 dispatch rules — could be trimmed or split for clarity, matching the level-4 anchor rather than the fully lean level-5. | 4 / 5 |
Actionability | The guidance is fully executable: exact copy-paste commands ("uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent"), concrete fallback merge rules ("Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace..."), and a Conventions section that resolves every placeholder used. | 5 / 5 |
Workflow Clarity | The eight activation steps are clearly sequenced with explicit error-recovery branches ("If the script is not found... offer to run the `bmad` skill's setup"; "If that skill is not installed, say so and offer to install it") and an explicit verification checkpoint ("confirm every entry was executed in order before proceeding"), matching the level-5 anchor with feedback loops and a checklist-style confirmation. | 5 / 5 |
Progressive Disclosure | The single-file body (~69 lines) is cleanly sectioned (## Overview, ## Conventions, ## On Activation with ### Steps 1-8), and all external material (customize.toml, team/user override tomls, resolver scripts, bmod.toml) is clearly signaled and loaded on demand one level deep — no bundle files exist to inline or bury. | 5 / 5 |
Total | 19 / 20 Passed |