modbender War Room
Structured adversarial evaluation of any strategic proposal using 5 parallel subagents.
Roles
| Role | Focus | Must Answer |
|---|---|---|
| Analyst | Data, math, quantitative modeling | "Show the numbers and formulas." |
| Guardian | Risk, failure modes, worst cases | "If [X] fails, what is the maximum loss?" |
| Treasurer | Resource efficiency, ROI, costs | "Per $1 invested, what is the expected return?" |
| Builder | Execution feasibility, timeline, tooling | "What is the time/cost/risk to implement?" |
| Strategist | Strategic fit, alternatives, long-term vision | "How does this fit the long-term strategy?" |
4-Phase Flow
Phase 1: Stance
State the proposal, key assumptions, and GO/NO-GO criteria.
Phase 2: Spawn Subagents
Spawn all 5 in parallel with sessions_spawn, mode: "run".
Token optimization (recommended for large proposals):
- Write proposal data to a temp file:
/tmp/rt_{topic}.md - Keep task prompts small (~500 tokens): role definition + deliverables + "Read /tmp/rt_{topic}.md for full context"
- Subagents use the
readtool to load the file themselves
This cuts input tokens by ~95% vs inlining all data in each prompt.
If the proposal is short (under 1500 words), inline it directly in the task prompt.
Label pattern: {role}_{topic}_{YYYYMMDD}
Phase 3: Collect and Critique
Wait for all 5 (auto-announced). Then apply the Critic lens:
- Consensus (4/5+ agree)
- Disputes and contradictions
- Stress-test: "If [X] fails, the entire logic collapses."
- Blind spots no agent raised
Phase 4: Ruling
Output document must include ALL sections:
- Participants table (role, label, runtime, key contribution)
- Per-agent summaries with numbers
- Consensus points
- Disputes with explicit rulings and rationale
- Final plan with concrete numbers
- Scenario projections (bull/base/bear with probabilities)
- Retained doubts (mandatory: intellectual honesty)
- Ruling: GO / NO-GO / REWORK + conditions
- Task list: P0/P1/P2 with owners and deadlines
Audit ID format: RT{N}-{TOPIC}-{YYYYMMDD}
Domain Adaptation
The 5 roles adapt to any domain. See references/domains.md for domain-specific mandatory questions and prompt guidance for: Finance, Product, Engineering, Hiring.
Role Details and Prompt Templates
See references/roles.md for full role definitions. See references/prompts.md for spawn patterns and ruling templates.
Post-Ruling Checklist
- Write ruling to a file and commit
- Store key decisions to long-term memory with audit ID
- Update daily log