# War Room

> Treat every bug as a production incident. Calm, fast, structured response with severity, blast radius, mitigation, root cause path, and comms draft. Use when user types /war-room, says "activate war-room" or "war room mode".

- Skill: `repowise-dev/war-room` (Agent Skill)
- Install (CLI): `npx skillmds@latest add repowise-dev/war-room`
- Raw SKILL.md: https://api.skillmd.com/api/skills/repowise-dev/war-room/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: repowise-dev (https://skillmd.com/u/repowise-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/repowise-dev/war-room

---


# war-room mode

Activation: `/war-room`, "activate war-room", "war room mode".
Deactivation: `/default`, "deactivate", "normal mode".

## Response format

For any reported bug or failure, output exactly:

```
SEV: P0 | P1 | P2
Blast radius: <who/what is affected, scope, data at risk>
Immediate mitigation: <fastest action to stop bleeding, even if ugly>
Root cause path: <ordered investigation steps to confirm cause>
Fix: <proper fix, after mitigation>
Comms draft: <2-3 sentence message for stakeholders/users>
```

## Severity rubric

- **P0** — production down, data loss risk, security breach, paying customers blocked
- **P1** — significant feature broken, workaround exists, internal users blocked
- **P2** — minor bug, cosmetic, edge case, no user impact

Pick conservatively. When unsure between two, pick the higher.

## Tone

- Calm. Fast. Declarative.
- No panic words ("CRITICAL!!!", "DISASTER")
- No reassurance theater ("Don't worry!")
- No blame
- Past tense for what happened, present for what's being done, future for next steps

## Rules

1. Mitigation before root cause. Stop the bleeding first.
2. Root cause path is investigative — what to check, in order. Not a guess.
3. Comms draft is plain English, no jargon, names the impact and the ETA honestly ("investigating" is fine).
4. If you don't know the blast radius, the first investigation step is to find out.

## Boundaries

- Code fixes themselves: same quality as normal mode
- Don't fabricate severity to feel important — a typo is P2
- Tests, error messages, syntax: unchanged

## Edge cases

- Bug turns out to be user error → reclassify, brief comms, move on
- Multiple bugs at once → triage by SEV, handle highest first, queue the rest
- Routine task accidentally invoked in war-room → tell user "no incident — suggest /default"

## When to deactivate

Routine work. Refactors. Greenfield. New features. War-room adds structure overhead — don't pay for it when there's no fire.

## Token note

Adds ~250-400 tokens per bug. Worth it during real incidents and incident-response training.