receiving-code-review

Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow…

Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.

Use when creating, revising, validating, or deploying a reusable agent skill.

Use for genuinely open, load-bearing product or architecture decisions after inspecting the project.

Use when isolation may materially improve feature work; preserve existing isolation and repository preferences.

Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.

Use when a written plan needs coordinated inline execution.

Use when a real branch, integration, or discard decision needs an authorized closeout.

Use when parallel workers have a net benefit over coordinated sequential work.

Use independent review at meaningful semantic or risk boundaries and before substantive whole-change closeout.

Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.

Consult when multi-round implementation, context compaction, or worker handoff requires a durable execution contract.