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.
An exceptionally well-structured autonomous-review procedure: concrete executable commands at every phase, explicitly sequenced validation checkpoints with feedback loops, and exemplary use of a one-level-deep reference bundle indexed by a category README. The only deductible is a modest amount of rhetorical justification and rule restatement that could be tightened.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and policy-driven rather than explanatory — it does not teach concepts Claude already knows, and nearly every sentence carries a directive or disambiguation. Minor instances of over-explanation could be trimmed (e.g. justificatory flourishes like "a wrong approve ships the defect with a green checkmark" and near-duplicate statements of the assumptions/one-terminal-call rules in the Behavior Rules section), keeping it below the lean-every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Fully executable commands throughout: exact `gh pr view --json` field lists, a copy-paste-ready GraphQL query with pagination instructions, `env -u GH_TOKEN -u GITHUB_TOKEN pnpm --filter <pkg> test`, `git rev-parse -q --verify MERGE_HEAD`, `gh pr review --body-file`, and artifact paths like `.artifacts/factory-review/pr-<number>.md`. Concrete commands cover the common cases of every phase. | 5 / 5 |
Workflow Clarity | Six clearly sequenced phases with explicit validation checkpoints and feedback loops: pending-bot polling (60s/10min) with a proceed-with-disclosure rule, head-SHA check before publishing with re-review-on-movement, transition-rejection retry with the reason addressed first, a six-item approval-gates checklist, and a mandatory adversarial check before every approve. This matches the top anchor including checklists for complex processes. | 5 / 5 |
Progressive Disclosure | The body keeps the workflow and navigation inline while the bulk of domain detail (15 category pages, indexed by a README table with a "when relevant" column, plus `references/archaeology.md` for command recipes) lives one level deep in the bundle — both referenced paths exist and are explicitly loaded at the right phase ("Load the category guidance before opening the diff"). Structure and navigation are exemplary: category guidance is appropriately split out with per-page relevance triggers rather than inlined. | 5 / 5 |
Total | 19 / 20 Passed |