War Room
After a war-room Phase 5 vote, capture rejected COAs and dissenting-view future work into deferred backlog items so strategic options are not lost.
Overview
War-room deferred capture is an agent skill most often used in Build PM (also Operate iterate) that records rejected COAs and dissenting future-work items after Phase 5 war-room voting.
Install
npx skills add https://github.com/athola/claude-night-market --skill war-roomWhat is this skill?
- Runs immediately after Supreme Commander publishes the final decision document and before the war-room session closes
- Captures eliminated COAs that received at least one Borda vote via deferred_capture.py CLI
- Scans Dissenting Views for future-work phrases (“should revisit”, “worth exploring”, “consider in phase N”)
- Skips zero-vote COAs to avoid noise while preserving minority-backed alternatives
- Captures COAs eliminated in Phase 5 only if they received at least one Borda vote
Adoption & trust: 1 installs on skills.sh; 304 GitHub stars; 0/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
Your agent war-room kills alternative COAs in voting, but rejected strategies and dissenting ideas never land in a backlog you can revisit.
Who is it for?
Builders using Claude Night Market / strategeion war-room flows who run formal COA voting and need backlog continuity for minority options.
Skip if: Casual single-prompt planning without COA artifacts, Borda votes, or a Supreme Commander decision document—run the full war-room stack first.
When should I use this skill?
Immediately after Phase 5 voting when the Supreme Commander publishes the final decision document and before the war-room session closes.
What do I get? / Deliverables
Rejected and dissent-tagged COAs become structured deferred items with context and artifact paths via deferred_capture.py before the session closes.
- Deferred backlog entries for voted-but-rejected COAs
- Deferred items parsed from Dissenting Views future-work language
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Deferred capture closes structured decision sessions during product/agent planning—canonical shelf is Build PM where COAs and roadmap tradeoffs are managed. PM subphase holds multi-agent deliberation artifacts, voting outcomes, and backlog hygiene when not every COA ships in the current slice.
Where it fits
Close a feature war-room and file rejected COAs that one expert still ranked highly.
Wire deferred items into your agent backlog after multi-role deliberation on tool choices.
Pull deferred COAs from a past session when replanning the next quarter roadmap.
How it compares
Integration step after group decision-making, not a lightweight brainstorming substitute or generic TODO app.
Common Questions / FAQ
Who is war-room deferred capture for?
Solo builders orchestrating multi-expert agent war rooms with documented COAs, Phase 5 voting, and strategeion artifact paths who need deferred backlog hygiene.
When should I use war-room deferred capture?
Use it in Build PM right after the final decision doc is published; in Operate iterate when archiving a strategy session; or whenever Dissenting Views list phased follow-ups you might schedule later.
Is war-room safe to install?
The skill invokes a local Python script with session metadata—review script behavior and repo trust on the Security Audits panel for athola/claude-night-market before running in production repos.
SKILL.md
READMESKILL.md - War Room
# Deferred Capture After Phase 5 (Voting and Narrowing), capture rejected COAs and any future-work items from the Dissenting Views section so nothing valuable is lost. ## When to Run Run this module immediately after the Supreme Commander publishes the final decision document and before the war-room session closes. ## Capturing Rejected COAs For every COA that was eliminated during voting, check whether it received at least one Borda vote. If it did, capture it as a deferred item: ```bash python3 scripts/deferred_capture.py \ --title "COA: <coa-title>" \ --source war-room \ --context "<rejection rationale from Supreme Commander>" \ --artifact-path "<path to coa file in strategeion>" \ --session-id "<war-room-session-id>" ``` A COA that received zero Borda votes across all expert roles does not need to be captured. ## Capturing Dissenting-View Items After capturing rejected COAs, scan the "Dissenting Views" section of the Supreme Commander decision document. For each item that describes future work (identified by phrases such as "should revisit", "worth exploring", "consider in phase N"), capture it using the same script: ```bash python3 scripts/deferred_capture.py \ --title "COA: <coa-title>" \ --source war-room \ --context "<rejection rationale from Supreme Commander>" \ --artifact-path "<path to coa file in strategeion>" \ --session-id "<war-room-session-id>" ``` Use the dissenting view text as the `--context` value. Omit `--artifact-path` if no coa file corresponds to the item. ## Behavior Rules - Capture is automatic: do not prompt the user for confirmation. - Capture every qualifying COA in a single pass before closing the session. - If `scripts/deferred_capture.py` is not present in the repository, log a warning and skip capture rather than blocking the war-room close. - The session ID must match the ID stored in `.attune/war-room-session.json`. --- name: deliberation-protocol description: Phase definitions and flow control for War Room deliberation sessions category: war-room-module tags: [protocol, phases, workflow] dependencies: [] estimated_tokens: 800 --- # Deliberation Protocol ## Session Lifecycle ``` Initialize | v +------------------------+ | Phase 0: Reversibility | <-- Chief Strategist (immediate) | Assessment | +------------------------+ | +---> [RS ≤ 0.40: EXPRESS MODE - skip to Phase 7] | v +-------------------+ | Phase 1: Intel | <-- Scout + Intel Officer (parallel) +-------------------+ | v +-------------------+ | Phase 2: Assess | <-- Chief Strategist +-------------------+ | v +-------------------+ | Phase 3: COA Dev | <-- Multiple experts (parallel, anonymized) +-------------------+ | v +-------------------+ | Escalation Check | <-- Supreme Commander decides +-------------------+ | +---> [Escalate to Full Council if needed] | v +-------------------+ | Phase 4: Red Team | <-- Red Team Commander +-------------------+ | v +-------------------+ | Phase 5: Voting | <-- All active experts +-------------------+ | v +-------------------+ | Phase 6: Premortem| <-- All active experts (parallel) +-------------------+ | v +-------------------+ | Phase 7: Synthesis| <-- Supreme Commander +-------------------+ | v Persist to Strategeion ``` ## Phase Definitions ### Phase 0: Reversibility Assessment **Purpose**: Determine appropriate deliberation intensity before committing resources. **Expert**: Chief Strategist (Sonnet) **Execution**: Immediate, before any other phases **Inputs**: - Problem statement - Initial context **Step 0a: Threshold Configuration** (optional) Prompt user for custom thresholds: ``` Reversibility Thresholds (Enter for defaults): Express ceiling [0.40]: _ Lightweight ceiling