red-team-reviewlisted

# Red Team Review Loop An iterative review loop where research is bundled via `context-bundler` and dispatched to one or more adversarial reviewers. The loop continues until the red team approves. ## When to Use - Architecture or design decisions that need adversarial scrutiny - Research findings that need epistemic validation - Security analysis that needs independent verification - Any work product where "more eyes" reduce risk ## Process Flow 1. **Research & Analyze** — Deep-dive into the problem domain. Create analysis docs, capture sources. 2. **Review Packet Generation** — Prepare the context for the reviewer: - **Create Prompt**: Write or update a `red-team-prompt.md` explaining exactly what is being reviewed and what the reviewer should focus on. - **Define Manifest**: Update a `manifest.json` or equivalent list dictating which source files and research artifacts to include. - **Bundle Context**: Execute the `context-bundler` plugin, feeding it the manifest and prompt, to compile a single cohesive review packet. - **Iteration Directory Isolation**: Bundle the context and save the output to explicitly isolated directories (e.g., `.history/review-iteration-1/`) so that when the Red Team forces a rewrite, the baseline artifact is never destructively overwritten. 2.5. **Interactively Determine CLI and Model (ask once during bootstrap)**: Before dispatching context bundles to CLI agents: - Interactively ask the user: *"Which LLM CLI backend should be us