Skip to content

hashgraph-online/awesome-codex-plugins / plugins/beastlabai/multi-llm-plugin/skills/multi-llm

multi-llm

Flagged

Orchestrate plan reviews, task generation, implementation and code reviews across several LLM CLIs in parallel, or ask every model one free-text question about a plan. Use when the user says: review my plan, multi-llm, run a code review, generate tasks from a plan, implement this plan, ask the models about my plan.

FileKindSize
SKILL.mdskill md4.0 KB
apply_code_fixes_orchestrator.pyscript57.0 KB
apply_commit_fixes_orchestrator.pyscript2.3 KB
apply_suggestions_orchestrator.pyscript4.6 KB
apply_task_suggestions_orchestrator.pyscript19.2 KB
ask_orchestrator.pyscript162.5 KB
assets/icons/Anthropic.svgother584 B
assets/icons/Codex.svgother1.3 KB
assets/icons/Copilot.svgother1.5 KB
assets/icons/Cursor.svgother793 B
assets/icons/GoogleGemini.svgother623 B
assets/icons/Goose.svgother3.2 KB
assets/icons/Kilocode.svgother531 B
assets/icons/MiniMax.pngbinary1.5 KB
assets/icons/Mistral.svgother717 B
assets/icons/MoonshotAI.svgother957 B
assets/icons/Nvidia.svgother2.4 KB
assets/icons/OhMyPi.svgother434 B
assets/icons/OpenAI.svgother1.7 KB
assets/icons/Opencode.svgother325 B
assets/icons/Pi.svgother440 B
assets/icons/Qwen.svgother1.7 KB
assets/icons/Zhipu.pngbinary442 B
assets/icons/xAI.svgother343 B
assets/omp/overlay.ymlconfig2.4 KB
check_workflow_prerequisites.pyscript77.8 KB
code_review_orchestrator.pyscript326.3 KB
display_decisions.pyscript9.8 KB
finalize_tracking.pyscript1.3 KB
full_workflow_orchestrator.pyscript69.7 KB
generate_tasks_orchestrator.pyscript44.2 KB
hosts/capabilities.yamlconfig50.2 KB
hosts/codex/plugin-skill.md.tmplother2.8 KB
hosts/codex/shim.md.tmplother7.3 KB
hosts/opencode/plugin-command.md.tmplother2.2 KB
hosts/opencode/shim.md.tmplother6.8 KB
hosts/render_capabilities.pyscript48.4 KB
hosts/snippets/poll-loop.mdmarkdown4.4 KB
hosts/snippets/uv-preflight.mdmarkdown2.2 KB
hosts/uv-missing.txtmarkdown1.5 KB
implement_orchestrator.pyscript156.4 KB
improve_code_orchestrator.pyscript1.6 KB
improve_commits_orchestrator.pyscript2.5 KB
improve_plan_orchestrator.pyscript1.6 KB
init_config.pyscript58.0 KB
instructions/apply-code-fixes.mdmarkdown56.2 KB
instructions/apply-commit-fixes.mdmarkdown10.3 KB
instructions/apply-suggestions.mdmarkdown48.9 KB
instructions/apply-task-suggestions.mdmarkdown54.5 KB
instructions/ask.mdmarkdown27.6 KB
instructions/full-workflow.mdmarkdown25.3 KB
instructions/generate-tasks.mdmarkdown18.1 KB
instructions/implement.mdmarkdown55.8 KB
instructions/improve-code.mdmarkdown25.7 KB
instructions/improve-commits.mdmarkdown25.5 KB
instructions/improve-plan.mdmarkdown26.7 KB
instructions/init-config.mdmarkdown6.6 KB
instructions/review-code.mdmarkdown44.0 KB
instructions/review-commits.mdmarkdown11.4 KB
instructions/review-plan.mdmarkdown38.8 KB
instructions/review-tasks.mdmarkdown38.2 KB
modes.pyscript58.8 KB
multi_llm.pyscript101.1 KB
prompts/ask.txtmarkdown948 B
prompts/code_review.txtmarkdown4.5 KB
prompts/commit_review.txtmarkdown6.2 KB
prompts/consolidate_suggestions.txtmarkdown3.1 KB
prompts/implementation_task.txtmarkdown1.4 KB
prompts/plan_review.txtmarkdown8.0 KB
prompts/task_review.txtmarkdown8.3 KB
providers.yamlconfig20.7 KB
pyproject.tomlmanifest7.0 KB
references/apply-write-executor.mdmarkdown3.5 KB
references/consolidation.mdmarkdown5.6 KB
references/host-capabilities.mdmarkdown13.5 KB
references/human-decision-batch.mdmarkdown17.2 KB
references/implement-prerequisites.mdmarkdown6.0 KB
references/implement-write-executor.mdmarkdown5.4 KB
references/interrupted-run-recovery.mdmarkdown3.1 KB
references/own-check.mdmarkdown4.3 KB
references/resume-detection.mdmarkdown8.5 KB
references/revalidation.mdmarkdown6.9 KB
references/review-code-apply-fixes.mdmarkdown4.3 KB
references/salvage-handling.mdmarkdown12.5 KB
references/summary-format.mdmarkdown10.0 KB
references/uv-check.mdmarkdown5.7 KB
references/wave-batching.mdmarkdown5.2 KB
review_commits_orchestrator.pyscript2.3 KB
review_plan_orchestrator.pyexecutablescript24.6 KB
review_tasks_orchestrator.pyscript10.7 KB
schemas/cascade_record.schema.jsonconfig6.6 KB
schemas/code_review_issues.schema.jsonconfig2.0 KB
schemas/consolidated.schema.jsonconfig6.8 KB
schemas/consolidation_batch.schema.jsonconfig3.7 KB
schemas/generated_tasks.schema.jsonconfig3.1 KB
schemas/host_capabilities.schema.jsonconfig38.3 KB
schemas/human_decision_verdicts.schema.jsonconfig2.6 KB
schemas/result_line.schema.jsonconfig10.1 KB
schemas/review_suggestions.schema.jsonconfig2.4 KB
schemas/state_file.schema.jsonconfig23.3 KB
schemas/status_file.schema.jsonconfig24.9 KB
schemas/status_json.schema.jsonconfig10.8 KB
schemas/subagent_tasks.schema.jsonconfig20.5 KB
schemas/task_decomposition.schema.jsonconfig1.2 KB
schemas/write_batch_result.schema.jsonconfig8.8 KB
templates/config/providers.override.yamlconfig17.8 KB
templates/consolidated_report_template.htmlother44.1 KB
templates/pr_report_template.htmlother181.2 KB
templates/report_template.htmlother67.5 KB
templates/shared/report_core.cssother4.1 KB
templates/shared/report_core.jsscript25.5 KB
update_plan_tasks.pyscript20.9 KB
utils/__init__.pyscript284 B
utils/advisory.pyscript4.8 KB
utils/apply_orchestrator_base.pyscript229.0 KB
utils/apply_output_helpers.pyscript10.9 KB
utils/apply_path_helpers.pyscript683 B
utils/apply_report.pyscript51.6 KB
utils/apply_selection_helpers.pyscript6.8 KB
utils/apply_suggestion_phase.pyscript11.7 KB
utils/atomic_io.pyscript12.9 KB
utils/attempt_classifier.pyscript33.2 KB
utils/backup.pyscript2.0 KB
utils/batch_done.pyscript81.3 KB
utils/batch_ledger.pyscript27.7 KB
utils/batch_prompt.pyscript30.1 KB
utils/batch_prompt_builder.pyscript13.2 KB
utils/batch_reply.pyscript32.9 KB
utils/batch_suppressions.pyscript15.5 KB
utils/cascade_archive.pyscript50.6 KB
utils/cascade_ledger.pyscript39.3 KB
utils/cascade_provenance.pyscript22.0 KB
utils/check_records.pyscript59.7 KB
utils/check_reply.pyscript9.5 KB
utils/check_tree.pyscript1.2 KB
utils/cli_common.pyscript94.3 KB
utils/cli_version_cache.pyscript14.0 KB
utils/clock.pyscript3.5 KB
utils/code_fix_batcher.pyscript31.4 KB
utils/codex_trust.pyscript12.9 KB
utils/commit_apply.pyscript73.3 KB
utils/commit_attribution.pyscript21.2 KB
utils/commit_brief.pyscript32.2 KB
utils/commit_front_door.pyscript81.9 KB
utils/commit_paths.pyscript18.0 KB
utils/commit_range.pyscript61.2 KB
utils/commit_report.pyscript19.9 KB
utils/commit_review.pyscript413 B
utils/commit_spelling.pyscript7.9 KB
utils/commit_write_guard.pyscript9.9 KB
utils/concurrency.pyscript11.6 KB
utils/consolidation.pyscript89.0 KB
utils/detach.pyscript187.9 KB
utils/dispatch_spawn.pyscript62.4 KB
utils/doctor.pyscript76.7 KB
utils/env_vars.pyscript20.5 KB
utils/failure_capture.pyscript10.1 KB
utils/file_discovery.pyscript11.0 KB
utils/filtering.pyscript19.9 KB
utils/fresh_reset.pyscript3.9 KB
utils/git_diff.pyscript23.6 KB
utils/git_utils.pyscript86.6 KB
utils/held_folder.pyscript21.3 KB
utils/host_capabilities.pyscript48.0 KB
utils/host_install.pyscript77.6 KB
utils/host_paths.pyscript12.0 KB
utils/host_routes/__init__.pyscript5.7 KB
utils/host_routes/codex.pyscript18.3 KB
utils/host_routes/npm.pyscript12.2 KB
utils/host_shim.pyscript14.7 KB
utils/html_report_generator.pyscript118.9 KB
utils/human_decisions.pyscript38.3 KB
utils/human_task_plan.pyscript30.2 KB
utils/importance.pyscript6.2 KB
utils/improve_cascade.pyscript63.7 KB
utils/improve_cascade_next.pyscript22.2 KB
utils/improve_steps.pyscript33.1 KB
utils/improve_workflow.pyscript120.9 KB
utils/interactive.pyscript31.6 KB
utils/json_extractor.pyscript83.1 KB
utils/judge_vocab.pyscript5.3 KB
utils/known_checks.pyscript41.6 KB
utils/landlock_dispatch.pyscript103.8 KB
utils/landlock_exec.pyscript21.4 KB
utils/launch_limiter.pyscript13.5 KB
utils/llm_client.pyscript142.7 KB
utils/manual_tasks.pyscript14.9 KB
utils/metrics.pyscript68.1 KB
utils/next_phase.pyscript96.7 KB
utils/next_phase_words.pyscript6.4 KB
utils/output_handler.pyscript23.2 KB
utils/phase_walk.pyscript6.4 KB
utils/plan_updater.pyscript17.9 KB
utils/positionals.pyscript5.8 KB
utils/prior_changes.pyscript28.7 KB
utils/probe_state.pyscript17.9 KB
utils/process_capture.pyscript44.1 KB
utils/process_control.pyscript228.7 KB
utils/process_state.pyscript6.6 KB
utils/progress_tracker.pyscript92.2 KB

references/resume-detection.md

View on GitHub
# Resume Detection

Check for existing output BEFORE running the orchestrator to avoid expensive duplicate runs.

The review cores' resume step runs `util resume-state <mode> <plan>`, which makes these checks
itself, read-only, and prints the case and the action as one `[RESUME_STATE]` line. This file is
what that line means; with the command unavailable, make the same checks by hand.

Two rules hold throughout. Only `state.json` completes a phase: files on disk never do. And no file
date says which round wrote a file (a clock set back, a copy that kept its dates or a coarse file
system all mislead): the `round_id` a fan-out stamps into `.status.json` and every file of its round
records does, and for a file from before round ids, `.status.json`'s `validation_pending` beside the
task file. When a validation file is another round's, or nothing proves whose it is, the answer is a
`--force` re-run (case c), which may re-run work but never reports an earlier round's verdicts as
this one's.

## Detection Cases

<!-- BEGIN GENERATED: resume cases (utils/resume_state.py) -->
Check in this order; the first case that matches is the answer. `util resume-state` prints it as `[RESUME_STATE] case=<a-f> action=<word> models=<…> batches=<…> flags=<…> ownership=<…>`.

a. If `state.json` records the phase complete: the orchestrator's own completed-phase guard. Files on disk never make a phase complete: a `--force` re-run leaves the previous round's `validation.json` and `report.md` in place until it regroups:
   -> The phase is complete. Report results from `{plan}/{phase}/report.md` (or `report.html`) and skip (`report`). While `.status.json` records `checkpoint_recovered`, a note on stderr says so: the report was built from the answers the run that completed it checked, and a later run of the phase reuses no file in the folder.

b. If `{plan}/{phase}/validation_tasks.json` is this round's and lists its batches, no validation file is another round's (c), and `validation_batch_*.json` files exist (a retired round's `*.stale.json` does not count). This round's: the task file records the `round_id` `.status.json` beside it records (a fan-out stamps a fresh one there before it replaces any file); where either records none (written before round ids), when `.status.json` reads `state: "validation_pending"` (a run writes that word right after the task file, and the next fan-out's first write replaces it):
   -> Validation ran partially or fully. If every batch the task file lists has its `validation_batch_<N>.json`: run `--reaggregate` to finalize (`reaggregate`). If some are missing: run only the validation tasks of the missing batches (`batches=` names them), then reaggregate (`validate`).

c. If `validation.json`, `validation_tasks.json` or a `validation_batch_*.json` exists in `{plan}/{phase}/`, but nothing proves them this round's as in b and f: the task file or `validation.json` records a `round_id` other than the one `.status.json` records (`ownership=stale`: an earlier round's file a re-run stopped before replacing), or, where either records no round id, the checkpoint reads another state (a re-run's `models_running`, `models_complete` or `grouping_complete`, or a `complete` that `state.json` no longer records), or there is no checkpoint, no readable task file, or validation files without a task file (`ownership=uncertain`). No file date settles it:
   -> Reporting, reaggregating or validating them could finish the phase on an earlier round's verdicts. Run the orchestrator again with `--force` (every phase) and the models `models_requested` records (`rerun`, `ownership=stale` or `ownership=uncertain`; `models=-` when none is recorded: launch with the selection the core would make). It keeps each reusable model result (`[SKIP]`), regroups, retires the verdicts its grouping does not bind and validates again. Never `--rerun-all`.

d. If no validation file (as in c), but per-model `*.json` result files (or a `grouped.json`) exist in `{plan}/{phase}/`, or `.status.json` reads a fan-out stage (`models_running`, `models_complete`, `grouping_complete`) and lists `models_requested`; or `.status.json` records `checkpoint_recovered` and `state.json` records the phase neither complete (a) nor stale (e), whatever files are there (checked right after a: an earlier run replaced the phase's damaged checkpoint, so no file in the folder counts, validation files included, and a `--reaggregate` refuses it); or `.status.json` exists but cannot be read (checked right after a too: a `--reaggregate` refuses it, and only a fresh run recovers a damaged one):
   -> The fan-out stopped before validation. Compare the files with `models_requested` in `{plan}/{phase}/.status.json`; a file counts when the fan-out would keep it (non-empty, a JSON list, and on review-code tied by the scope ledger `.review-scope.json` to the scope `review-scope.md` records). If every requested model has its file: run `--reaggregate`. If some have none: run the orchestrator again with the same models. With no file at all that is still the original run's whole selection. It keeps each file (`[SKIP]`) and runs only the missing ones; a `--reaggregate` would report without them. On review-code add `--force`, which a dir holding results or an earlier round's files needs (exit 3 otherwise); a composite's flags line already carries it. Never `--rerun-all`. Left out, `--scope-policy` stays the one the kept files were requested under (one `Scope policy notice:` line says so); a different one typed stops at exit 3 with `[SCOPE_POLICY_CONFLICT]`. The first answer is `reaggregate`; the second is `rerun`, its `models=` listing every requested model. Over a checkpoint that cannot be read the answer is `rerun` with `models=-`: nothing records the selection, so launch with the one the core would make; the fresh run recovers a damaged checkpoint, reusing no file in the folder, and a note on stderr says what to do when it cannot.

e. If none of the other cases; or `state.json` records a code review completed before the latest implement (checked first: its files are out of date):
   -> Nothing to resume: run the orchestrator as planned (`run`). A code review older than the latest implement is re-run as `--force` by the orchestrator itself; while its `.status.json` records `checkpoint_recovered`, a note on stderr says the run reuses no file in the folder.

f. If `validation_tasks.json` is this round's and lists its batches, no validation file is another round's (both as in b), and NO `validation_batch_*.json` exists:
   -> The orchestrator handed validation over and none has run. Skip to Validation Handling: run every validation task, then reaggregate (`validate`).

The action words:

- `report`: the phase is complete: report its results and run no orchestrator.
- `reaggregate`: run the orchestrator's `--reaggregate`; no model runs.
- `validate`: go to the validation step: run the validation tasks (only the batches `batches=` names, when it names any), then `--reaggregate`.
- `rerun`: launch the orchestrator again with `--models` exactly as `models=` lists them (`-`: none recorded, so the selection the core would make) and the `flags=` added; models with a result keep it (`[SKIP]`).
- `run`: nothing to resume: launch the orchestrator as planned.

`ownership=` says why case c chose a `rerun` over the validation files on disk: `stale` when one records a review round other than the one `.status.json` records, `uncertain` when nothing recorded ties them to that run. Every other answer prints `ownership=-`.
<!-- END GENERATED: resume cases -->

## Orchestrator Guards

The orchestrator has its own re-run protection as defense-in-depth:
- **Primary**: Exits with code 2 if phase is already marked complete in state.json. Use `--force` to override.
- **Secondary** (code-review only): Exits with code 3 if partial completion artifacts exist without the phase being complete. It records the phase complete itself (exit 0) only when `validation.json` and `report.md` both record the round `.status.json` records and `report.md` is the whole report built from that `validation.json` (its round line's digests); a task file or `validation.json` of another round, or a task file nothing ties to this run, sends it to `--force` instead, and a report that is not this round's, cut short or older than the verdicts sends it to `--reaggregate`.
- **Reaggregate** (every review phase): `--reaggregate` refuses at exit 3 when the task file or `validation.json` records another round than `.status.json`, naming the `--force` re-run.

This instruction-level resume detection is the FIRST line of defense; the orchestrator guards are backup protection.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall