execution-plan-review
Show a milestone's per-issue ordering and execution assignments as one table, take the user's revisions, and sync the GitHub issues, which are the source of truth. milestoneplan is the read-only view of this table; it routes Execution-block fixes here.
Steps
1. Render the table from the issues, not from memory
Fetch every milestone issue (gh issue list --milestone "<title>" --json number,title,body, with the title quoted) and parse the ## Execution blocks (read a legacy fableplan first: line as plan first:, and write back only plan first:):
| Issue | C | Depends on | Runs after | Build model | Effort | Validate | plan first? | Plan |
|---|
Cell rules:
- Validate is the effective
<model> · <effort>the pipeline dispatches. The model comes from the[C<score>]band (a missing prefix routes as band 3) unless aValidate model:line stampsFable 5.1,Opus 5.5, or<Name> (Codex CLI[, <model-id>]); the effort is the band default unless aValidate effort:line stamps one. Thevalidate-issuestep 6 band table is the authority; do not restate it. Show a stamp asFable 5.1 · low (stamped; band Opus 5.5 · high)orAstra · low (Codex CLI, gpt-6-astra; stamped; band Opus 5.5 · high), and a clamp asOpus 5.5 · high (stamped low → high: low is a Fable-only tier). Onlylowclamps on an Opus validate;mediumruns as stamped. When the user gives a skip list (issue numbers, or "all", they plan to pass tomilestone-workflowasskipValidate), a listed issue showsskipped (run arg)when no open in-milestone predecessor (Depends onorRuns after), missing[C..]prefix, or missing Execution block predicts a fallback; otherwise it keeps the route with(listed; validates: <reason>). Add one note line that the run checks the evidence, the edit history, and the base branch at run time, and validates any issue that fails a check. The skip list is a run arg: never write it into an issue. - Effort shows the tier the pipeline runs. A Claude build runs only at
high, so a Claude row stamped any other tier shows the clamp, e.g.high (stamped xhigh → high: Claude builds run at high only), the same waymilestoneplanshows it. A Codex CLI or Cursor CLI build shows its stamped tier. - Plan shows
<model> · <effort>onplan first: Yesissues: the model defaults toOpus 5.5, and on an Opus 5.5 plan the effort defaults toxhighwhen the score is 85 or higher (or the title has no score) and tohighbelow 85; a Fable plan runs only athigh; a stampedPlan model:orPlan effort:line shows its value with(stamped). On aNoissue show—only when no line is stamped; any stamped line, a default value included, shows as<stamp> (inert — no plan stage runs). - An absent ordering field shows as
missing, nevernone.
Then add 2–3 sentences on the pattern (dominant bands, which issues plan first at score ≥ 75, the review trigger) as a sanity check against the validate-issue step 6 band table.
2. Take revisions
- Shorthand: "11 should be medium", "12 depends on 8 and 9", "13 runs after 12", "clear 14's dependencies", "plan 17 at medium", "validate 271 at medium". Resolve row-vs-issue ambiguity against the table just shown; confirm in half a sentence when still ambiguous. A bare effort revision means the build effort; confirm in half a sentence when the issue also has a plan stage.
- External CLI builds ("build 275 with luna on codex at max", "277 grok on cursor high", "278 on cursor with cursor-grok-4.6-high") write
- **Build model:** <Name> (Codex CLI)or<Name> (Cursor CLI), with, <model-id>inside the parenthetical when the user names an id, and the tier toEffort:.maxis a Codex CLI-only tier: write a Cursormaxasxhigh. A Claude build runs only athigh, so write every other tier on a Claude build, Fable included, ashigh; say the clamp applied. - "validate at " writes
- **Validate effort:** <tier>; "validate with fable" or "validate with fable at low" writes- **Validate model:** Fable 5.1(orOpus 5.5) plus any tier; "validate 20 with astra on codex at low" writes- **Validate model:** Astra (Codex CLI, <model-id>)with the id the user names and- **Validate effort:** low(lowtomax); "plan at " writes- **Plan effort:** <tier>; "plan with fable" writes- **Plan model:** Fable 5.1, and the default Opus 5.5 plan needs no line (an Opus plan stampedlowruns athigh). A revision that names the band default for that stage removes the line instead of stamping it; say so. A milestone-wide revision ("every Fable validate at medium", "all plans at medium", "validate both with fable on low") applies, in one batch, to every issue whose stage runs on that model after the batch. - Push back once when a revision conflicts with the score band (
validate-issuestep 6 /prd-to-issues): plan below score 75, or dropping below Opus on a money/security/irreversible-deletion issue. Give one recommendation with the reason; the user decides. - Batch revisions; do not round-trip to GitHub per message.
- A Plan effort revision on a
plan first: Noissue is inert. Say so once and drop it, or ask whether they meant to turn plan on. A flip toYesplans on Opus 5.5 at the score default (xhighat 85 or higher,highbelow) unless the same batch stamps aPlan model:orPlan effort:line. A flipYes→Noon an issue with aPlan model:orPlan effort:line strips every such line during write-back; say which lines you dropped. Offer once to strip any inert stamp already on an issue instead of silently carrying it forward. - Preserve the edge kind:
Depends onstays a hard prerequisite,Runs afterstays ordering-only. Never move an issue between the fields to simplify the graph. - Before writing: verify every referenced issue exists, reject self-references, deduplicate each list, reject a predecessor present in both fields, and recursively fetch referenced issues outside the milestone until the explicit ordering graph closes.
- Reject the whole batch before write-back if the combined graph (every
Depends onandRuns afteredge, including unchanged and external issues) contains a cycle. Edit no issue, and show the cycle path.
3. Write back
Load github-issue-format. For each changed issue, gh issue edit preserving the entire body and changing only the intended Execution block lines; the footer verb flips to Updated. Strip \r from gh-fetched bodies. When edits collide with concurrent issue edits, re-fetch and re-apply only your delta. Re-run the graph validation after any concurrent-edit re-fetch and before retrying a write.
4. Confirm
Re-render the final table once after all revisions land, and say it is what the milestone workflow will execute.
Failure modes
| Situation | Do this |
|---|---|
| An issue lacks an Execution block | Derive model, effort, and plan first: from the [C..] band per prd-to-issues. Stamp no Validate effort:, Plan model:, or Plan effort: line unless the user asked for that model or tier. Flag the backfilled block in the table |
| An issue lacks one or both ordering fields | Backfill from the approved prd-to-issues graph when available; otherwise infer from Approach/Problem, mark the value inferred in the table, and confirm before write-back |
| Revision references a row that does not exist | Show the table again; ask which issue they meant |
Revision puts a Claude build's effort at any tier other than high | Write high and say the clamp applied: every Claude build, Fable 5.1 included, runs only at high. A Codex CLI or Cursor CLI build accepts low to xhigh as stamped, and Codex also accepts max |
| Revision names an external CLI build or validate without a known default model id | Only Luna (Codex CLI), Astra (Codex CLI), and Grok (Cursor CLI) resolve an id; before writing, ask for the id in half a sentence and write it inside the parenthetical |
Revision puts a Fable 5.1 validate stage at xhigh | Write it as stamped. The revision is the explicit ask that permits xhigh on Fable; the unstamped default stays high (the LLM Attribution Footer section of CLAUDE.md owns this rule) |
Revision puts a Fable plan stage at any tier other than high | Remove the Plan effort: line and say the clamp applied: a Fable plan, on Fable 5.1 or any later Fable version, runs only at high |
| Revision names a validate model | Write - **Validate model:** Fable 5.1, Opus 5.5, or <Name> (Codex CLI[, <model-id>]); a stamped model overrides the band (validate-issue step 6). Reject a Cursor CLI validate and keep the prior stamp; say the pipeline runs a validate pass only in the Codex read-only file sandbox, and Cursor has no write boundary. Ask about any other Claude name in half a sentence |
| Revision names a validate effort | Write the Validate effort: line. A Fable validate (stamped) runs every tier low to xhigh as stamped; a Codex CLI validate runs low to max as stamped. An Opus validate (stamped, or unstamped at any score) runs medium, high, and xhigh as stamped and raises low to high; say so, and offer a Validate model: stamp as the way to reach a Fable or Codex validate |
A stamped Build model or Effort diverges from the issue's current [C..] band default | Apply validate-issue/issue-editing.md (Edit the title): a stamp at or above the band default on a field (a heavier model, a Fable 5.1 build, a Codex CLI or Cursor CLI harness, a higher effort on a Codex CLI or Cursor CLI build, plan first: Yes) is a deliberate override from any session. Keep it, and mark it in the table as stamped above band. Restamp a stamp below the band default up to the default and report it, unless the user names the lower stamp deliberate in this session, with the step 2 push-back; a lower effort is deliberate only on a Codex CLI or Cursor CLI build. A Claude build Effort: stamp other than high is no override: show the clamp per the Effort cell rule, restamp it to high on write-back, and report it. A run-time rescore keeps a harness or Fable 5.1 stamp and only adds plan first: Yes |
Revision flips plan first: Yes → No on a band-3 ([C75]+) issue | Write it and say the issue loses its plan stage. Build effort stays high |
| Revision names a plan effort | Write the Plan effort: line with low, medium, high, or xhigh. A revision to the issue's default tier (xhigh on an Opus plan at score 85 or higher or with no score, else high) removes the line. On a Fable plan, every tier runs at high (see the Fable plan row) |
| Revision names a plan model | Write the Plan model: line with Fable 5.1. A revision to Opus 5.5 removes the line. A Plan model revision on a plan first: No issue is inert, the same as a Plan effort revision |
