richkuo/rk-skills/execution-plan-review

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:):

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 a Validate model: line stamps Fable 5.1, Opus 5.5, or <Name> (Codex CLI[, <model-id>]); the effort is the band default unless a Validate effort: line stamps one. The validate-issue step 6 band table is the authority; do not restate it. Show a stamp as Fable 5.1 · low (stamped; band Opus 5.5 · high) or Astra · low (Codex CLI, gpt-6-astra; stamped; band Opus 5.5 · high), and a clamp as Opus 5.5 · high (stamped low → high: low is a Fable-only tier). Only low clamps on an Opus validate; medium runs as stamped. When the user gives a skip list (issue numbers, or "all", they plan to pass to milestone-workflow as skipValidate), a listed issue shows skipped (run arg) when no open in-milestone predecessor (Depends on or Runs 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 way milestoneplan shows it. A Codex CLI or Cursor CLI build shows its stamped tier.
• Plan shows <model> · <effort> on plan first: Yes issues: the model defaults to Opus 5.5, and on an Opus 5.5 plan the effort defaults to xhigh when the score is 85 or higher (or the title has no score) and to high below 85; a Fable plan runs only at high; a stamped Plan model: or Plan effort: line shows its value with (stamped). On a No issue 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, never none.

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 to Effort:. max is a Codex CLI-only tier: write a Cursor max as xhigh. A Claude build runs only at high, so write every other tier on a Claude build, Fable included, as high; say the clamp applied.
• "validate <n> at <tier>" writes - **Validate effort:** <tier>; "validate <n> with fable" or "validate <n> with fable at low" writes - **Validate model:** Fable 5.1 (or Opus 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 (low to max); "plan <n> at <tier>" writes - **Plan effort:** <tier>; "plan <n> with fable" writes - **Plan model:** Fable 5.1, and the default Opus 5.5 plan needs no line (an Opus plan stamped low runs at high). 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-issue step 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: No issue is inert. Say so once and drop it, or ask whether they meant to turn plan on. A flip to Yes plans on Opus 5.5 at the score default (xhigh at 85 or higher, high below) unless the same batch stamps a Plan model: or Plan effort: line. A flip Yes → No on an issue with a Plan model: or Plan 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 on stays a hard prerequisite, Runs after stays 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 on and Runs after edge, 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