Content
66%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 highly actionable with an exceptionally clear phased workflow, exact commands, and explicit validation gates, but it is severely overlong due to heavy rule repetition and does no progressive disclosure at all — every contract, sub-mode, and config detail is inlined in one monolithic file. Deduplication plus splitting into reference files would address both weaknesses without losing the concrete guidance.
Suggestions
Move the omx question payload/answer-shape contracts, the five downstream handoff contracts, the autoresearch sub-mode, and the config/quality-gate reference into separate files under references/ and link to them from the body.
Deduplicate rules stated in multiple sections — the oversized-context summary gate, the answers[] read contract, and one-question-per-round each appear 3-5 times across Execution Policy, Phases, Tool_Usage, and the checklist; state each once authoritatively.
Collapse the Execution Policy section, which overlaps heavily with Phase 2 (pressure ladder, stage priority, oversized-context rules appear in both), into the phase where each rule is applied.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~575-line body is heavily padded with repetition: the oversized-context gate is stated in Execution Policy, Phase 0, Phase 2a, Tool_Usage, and the Final Checklist; the answers[0].answer contract repeats three times; 'one question per round' appears in multiple sections. It avoids explaining concepts Claude already knows (all content is project-specific), so it is not anchor 1, but it is noticeably below the midpoint — roughly half the file is duplicative and could be trimmed. | 2 / 5 |
Actionability | Fully executable guidance: exact commands ('omx state write --input '<json>' --json', 'OMX_QUESTION_RETURN_PANE=$TMUX_PANE omx question'), copy-paste-ready JSON payload and answer-shape contracts, exact artifact paths, weighted ambiguity formulas with explicit coefficients, TOML config keys, and a concrete placeholder-marker list for launch-readiness. Specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | Phases 0-5 are clearly sequenced with explicit stop conditions, readiness gates (Non-goals, Decision Boundaries), a pressure-pass requirement, blocking quality gates with a refine-and-re-run feedback loop, escalation conditions, a resume path, and a final checklist. Validation checkpoints and error recovery are explicit throughout. | 5 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/) and everything is inlined in a single 575-line file: omx question payload contracts, five full downstream-skill handoff contracts, the entire autoresearch sub-mode, the stride-contract JSON schema, and config documentation — all content that clearly belongs in separate reference files. Internal sections are well-labeled, which keeps it above a truly unstructured monolith, but nothing is disclosed progressively across files. | 2 / 5 |
Total | 14 / 20 Passed |