feat(commands): surface routing advice — triage, status, planning protocol (M16 16.3)#259
Merged
Merged
Conversation
…tocol (M16 16.3) Closes #254. - triage.yaml: routing_advice block - once a request routes to a focused-change or the five-step-loop, the host states the recommended tier/effort (advisory, ADR-0017); answer-directly needs none - doctor.py: opt-in --routing-milestone TITLE readout - one advisory line per open issue via route_advice (pure routing_lines helper); SKIP offline, never changes the exit code - .issues/README.md (new): the planning protocol - plan-doc Routing column + the Routing: body line + the sets-pattern/decision-heavy flags; commands/README + status.md updated - test_doctor.py: routing_lines checks (47/47 suite green) M15 backfill (#234-#250 body lines) runs as a tracker action alongside this PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
danielPoloWork
added
enhancement
danielPoloWork
added a commit
that referenced
this pull request
Jul 9, 2026
…rd (#260) The owner enriched the M15 backfill table (Title/Model/Effort columns, ultracode spelled as the Claude Code alias of max); on top: status -> in progress, a delivery record (16.1 #257 / 16.2 #258 merged, 16.3 #259 open, 16.4 queued on M15 #239), and the backfill marked APPLIED 2026-07-09 (owner-approved; Routing: lines written to #234-#250). Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #254 (M16 16.3). Plan:
.issues/M16-model-effort-routing-milestone.md· Policy #257 (16.1, ADR-0017) · Evaluator #258 (16.2).What
The advisory route now surfaces at the three read-points where work is actually picked up:
routing_advice:block intriage.yaml: once a request routes to afocused-changeor thefive-step-loop, the host also states the recommended tier + effort(
answer-directlyneeds none — no work is being routed).commands/README.mddocuments it./eados status—doctor.pygains an opt-in--routing-milestone "TITLE": one advisoryline per open issue (
#N -> tier/effort (model)) via a new purerouting_lineshelper overroute_advice. It degrades toSKIPwhenghis offline and never changes the exit code— advice is a readout, not a gate. Documented in
commands/status.md..issues/README.md: themilestone plan-doc format (with the
Routingcolumn M16's own plan already dogfoods) and theissue-filing rule — every filed issue body carries a
**Routing** (ADR-0017, advisory — reviewed YYYY-MM-DD): tier / effort — flags: …line, theflags recording what labels cannot say (
sets-pattern/decision-heavy).M15 backfill — ✅ APPLIED 2026-07-09 (owner-approved)
All 17 open M15 issues (#234–#250) now carry their reviewed
Routing:body line (idempotentappend; spot-checked #247 →
frontier-reasoning/max— flagsdecision-heavy,sets-pattern). The plan doc records the application and the owner's refined table (Title /Model / Effort columns; "ultracode" as the Claude Code alias of
max), plus a delivery recordfor 16.1–16.4.
Verification
run_all.py), incl. the newrouting_lineschecks intest_doctor.py;self-lint OK (the
triage.yamladdition parses under both loaders;.issues/**isallow-listed prose).
doctor.py <reference manifest> --routing-milestone "M16 — model & effort routing"prints the two remaining open M16 issues with correct advice([16.3] Surface routing advice: Step-0 triage,
/eados status, milestone-planning protocol (+ M15 backfill) #254 → standard/medium, [16.4] Auto-apply routing where the host allows: delegated subagent work carries model + effort #255 → fast/low label-only) plus the advisory boundary line.🤖 Generated with Claude Code