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` skill (dev-utils) in **Multi-Persona Fan-Out Mode**, feeding it the manifest and prompt, to compile one review packet per persona in the Graph Planning Phase 1 Fan-Out Trio: **Architecture Skeptic**, **Security / Edge-Case Auditor**, **TDD Contract Reviewer** — per `graph-planning-superpowers-policy.md` §2.2-2.3. Use a narrower single-persona bundle only when the review scope is genuinely single-dimensional (e.g. a pure security patch). - **Iteration Directory Isolation**: Bundle the context and save the output to explicitly isol