Overview
Therecursive-review-bundle subskill generates a durable, reproducible context bundle before you delegate an audit or review to a subagent. Without a canonical bundle, delegated reviews are context-free and cannot be accepted by the recursive-mode workflow.
When to Use
Use this subskill whenever you are delegating a Phase 3.5 code review, test review, or other audit to a subagent. Generate the bundle before dispatching the reviewer, and refresh it after any material repairs or scope changes.This subskill packages the handoff context. It does not replace the canonical workflow in
/.recursive/RECURSIVE.md and it does not perform the review itself.The Canonical Scripts
Two scripts ship with recursive-mode for generating review bundles:scripts/recursive-review-bundle.py— use when Python is availablescripts/recursive-review-bundle.ps1— use when the delegated path is PowerShell-oriented
Minimum Required Inputs
Every bundle invocation must include all of the following:
Add evidence refs or addenda paths explicitly when they are relevant — the bundle generator will also auto-discover applicable addenda and skill-memory refs.
Commands
Acceptance Rules
After generating the bundle, follow these rules before and after delegation:1
Record the bundle path
Record
Review Bundle Path in the delegated phase artifact. Without a recorded path, the phase cannot be considered properly delegated.2
Require the reviewer to cite the bundle
The reviewer must reference the bundle path, name the upstream artifacts they re-read, cite relevant addenda, reference the changed files or code they reviewed, and provide a final verdict. A bare bundle file is not proof of review quality — the written review must use the bundle contents.
3
Refresh after repairs
If material repairs or scope changes occur after the bundle was generated, regenerate it before sending to the reviewer. A stale bundle invalidates the review.