Content
70%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 exceptionally actionable and the enforced seven-step workflow is clearly sequenced with robust validation and error recovery. Its weaknesses are severe redundancy (the workflow, banner, and provider roles are each described multiple times) and a monolithic structure with no reference files to absorb examples and templates.
Suggestions
Collapse the duplicated sections: keep the Execution Contract as the single authoritative procedure and delete or heavily trim the "How It Works" Stages A-D and "Implementation Instructions" restatements, which repeat the same seven steps.
Move the ~100-line Example 1 and the full Problem Definition format template into a separate references/ file (e.g., references/examples.md) and reference it one level deep from the body.
Remove the duplicate banner specification in the "Visual Indicators" section by pointing back to the STEP 1 banner requirement (the comment already notes it lives there).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~790-line body is noticeably padded with duplication: the same seven-step workflow is restated three times (Execution Contract, "How It Works" Stages A-D, and "Implementation Instructions"), the provider banner is specified twice (STEP 1 and the "Visual Indicators" section), and Example 1 is a ~100-line fully worked sample, so well over a third of the tokens are redundant. | 2 / 5 |
Actionability | Guidance is fully executable: exact bash with plugin-root fallback chains, signal traps, and exit-status handling; a complete provider-check script; full AskUserQuestion option specifications; a precise orchestrate.sh invocation with validation and a recovery command; and a copy-paste output format template covering the common case. | 5 / 5 |
Workflow Clarity | Seven mandatory, explicitly blocking steps are sequenced with validation checkpoints at each boundary ("DO NOT PROCEED TO STEP N until..."), Step 5 verifies the synthesis report, error handling is specified per step, and failure paths include feedback loops (show logs, offer restore/discard, never fall back to direct analysis), matching the checklist-plus-recovery anchor. | 5 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so everything lives in one ~800-line file; the plugin-block references at the top are clearly signaled, but the worked examples and the full Problem Definition format template are inline content that clearly belongs in separate reference files, fitting the "some structure but could be better organized" anchor. | 3 / 5 |
Total | 15 / 20 Passed |