execution-plan-review
Use when the user wants to review or revise the ordering/model/effort/fableplan/plan-effort assignments on a milestone's GitHub issues — "review the execution plan", "/execution-plan-review", "show me the model assignments", or piecemeal revisions like "11 should be medium" or "plan 17 at xhigh". Renders the assignment table from the issues' Execution blocks, validates revisions, and writes them back. Stage 5 of the new-app-pipeline.
richkuo · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add richkuo/rk-skills --skill execution-plan-review技能说明
name: execution-plan-review description: Use when the user wants to review or revise the ordering/model/effort/fableplan/plan-effort assignments on a milestone's GitHub issues — "review the execution plan", "/execution-plan-review", "show me the model assignments", or piecemeal revisions like "11 should be medium" or "plan 17 at xhigh". Renders the assignment table from the issues' Execution blocks, validates revisions, and writes them back. Stage 5 of the new-app-pipeline.
execution-plan-review
Present the per-issue ordering and execution assignments as one table, absorb the user's revisions, and keep the GitHub issues (the single source of truth cold agents read) in sync. milestoneplan is the read-only view of the same table; it routes Execution-block fixes back here.
Steps
1. Render the table from the issues, not from memory
Fetch every issue in the milestone (gh issue list --milestone ... --json number,title,body) and parse the ## Execution blocks:
| Issue | C | Depends on | Runs after | Build model | Effort | Validate | fableplan first? | Plan effort |
|---|
Cell rules:
- Validate is the effective
<model> · <effort>the pipeline dispatches. The model derives from the[C<score>]band and is never stampable (a missing prefix routes as band 5); the effort is the band default unless aValidate effort:line stamps one. Thevalidate-issuestep 6 band table is the authority; do not restate it here. Show a stamp asFable 5.1 · medium (stamped; band high); show a clamp asOpus 5 · high (stamped <tier> → high: low/medium are Fable-only). - Plan effort defaults to
highonfableplan first: Yesissues; a stamped line shows as<tier> (stamped). On aNoissue show—only when no line is stamped; any stamped line,highincluded, shows as<tier> (inert — no plan stage runs), because the milestone pipeline logs it on every run and the source-of-truth table must not mask it. - An absent ordering field shows as
missing, nevernone, so legacy prose inference is not silently discarded.
Follow with 2–3 sentences on the pattern (dominant bands, which issues plan first at score ≥ 71, the review trigger) for 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), appending, <model-id>inside the parenthetical when the user names an id, and write the tier toEffort:.maxis a Codex CLI-only tier: a Cursormaxis written asxhigh, and a Claudemaxasxhighon every Claude model, Fable included; say the clamp applied. OnlyLunaon Codex andGrokon Cursor have a default model id; any other name needs an explicit id, so ask for one in half a sentence before writing. - "validate at " writes
- **Validate effort:** <tier>; "plan at " writes- **Plan effort:** <tier>. A revision that names the band default for that stage removes the line instead of stamping it, and say so. A milestone-wide revision ("every Fable validate at medium", "all plans at medium") applies to every issue whose stage runs on Fable, in one batch. - Push back once when a revision conflicts with the score band (
validate-issuestep 6 /prd-to-issues): fableplan below score 71, or dropping below Opus on a money/security/irreversible-deletion issue. One recommendation with the reason, then the user decides. - Batch revisions; do not round-trip to GitHub per message.
- A Plan effort revision on a
fableplan first: Noissue is inert. Say so once and drop it, or ask whether they meant to turn fableplan on. A flip toYesplans athighunless the same batch stamps aPlan effort:line. A flipYes→Noon an issue carrying aPlan effortline strips that line during write-back; say you dropped it. Offer once to strip any inert stamp already on an issue instead of carrying it forward silently. - 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.
3. Write back
Load github-issue-format. For each changed issue: gh issue edit preserving the entire body, changing only the intended Execution block lines; footer verb flips to Updated. Strip \r from gh-fetched bodies (the API returns CRLF). 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/fableplan from the [C..] band per prd-to-issues. Stamp no Validate effort: or Plan effort: line unless the user asked for a 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 |