resolve-reviewlisted

# Resolve a Review Out of Context `consult review` keeps the reviewer's working context out of the Host. This skill keeps the remediation loop out too. A resolution manager runs the review, triages the findings, lands and verifies the clear-cut fixes, and reports back only what the main thread must act on: rejected claims, escalations, and downstream impact. The main thread keeps building. ## Choose the reviewer The manager hosts the loop; it does not perform the review. The review itself is a Consult Job against a configured Profile, so the reviewing agent stays independent of both the main thread and the manager. Settle that choice in the main thread before anything is spawned — a native subagent cannot ask the user. Use the Profile and model the user already named; otherwise ask, proposing a strong model from a different Profile than the one that authored the change, since cross-provider review avoids shared blind spots. ## Spawn the resolution manager Pick the strongest available mechanism: 1. **Host with native subagents**: spawn one subagent using the Host's own mechanism and hand it the Procedure below verbatim. A native subagent keeps the Host's execution ability, so fixes come back verified. 2. **Host without native subagents**: let Consult host the manager as a deliberate inherited-authority Job: ```sh consult delegate --agent <profile> --write --sandbox inherit \ --background --label "resolve review" -- "<Procedure as a cold prompt>" `