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".
Install
$ agentstack add skill-repowise-dev-modpack-war-room ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-repowise-dev-modpack-war-room) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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:
Immediate mitigation:
Root cause path:
Fix:
Comms draft: 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
- Mitigation before root cause. Stop the bleeding first.
- Root cause path is investigative — what to check, in order. Not a guess.
- Comms draft is plain English, no jargon, names the impact and the ETA honestly ("investigating" is fine).
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: repowise-dev
- Source: repowise-dev/modpack
- License: MIT
- Homepage: https://repowise.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.