Thermos

Run two independent reviews of the same changes and synthesize their findings. This workflow explicitly delegates to two subagents when the host supports them.

Prepare

1. Resolve the review scope from the user's branch, PR, commit range, or working changes. Read repository guidance and record the repository path, base and head revisions, and included working changes. For a branch review, use the merge-base with the requested or verified base branch; do not assume main. Include untracked files only when they belong to the requested scope. Preparation is complete when both reviewers can identify the same changes.
2. Resolve the installed /thermo-nuclear-review and /thermo-nuclear-code-quality-review skills. They are required dependencies. Supply each reviewer its rubric's absolute SKILL.md path and have it read that file, or include the full rubric text when child contexts cannot access the skill. Child agents may not inherit skill discovery or parent context. If a dependency is missing, identify it and stop before presenting a Thermos verdict.
3. Gather the diff, changed-file list, relevant full-file contents, and known constraints. Give both reviewers the same scope and evidence, with repository access for tracing callers and related code. For a large diff, provide accessible artifact paths instead of truncated excerpts. List the repository guidance files already read and the rules from them that bear on the scope, so reviewers read further guidance only for paths that list does not cover. Finish preparation when the evidence and guidance list are accessible to both reviewers.

Delegate

Choose the branch matching the tools exposed in this session. Use the actual tool schema; tool names and parameters can vary between host versions. Use built-in agents without requiring custom agent registration, a plugin, a particular model, or an agent team.

Codex

Use the native spawn_agent tool, possibly exposed under a collaboration namespace, to launch two reviewers. Put the rubric and scope in each task message. Use separate task names when supported. Launch both before waiting for either. Collect both results with the host's native wait or completion mechanism, then close the completed agents if that host exposes a close tool.

Claude Code