---
name: war-room
description: Spin up an AI startup "war room" — a C-suite (CEO/CTO/CPO/CMO/COO) plus their teams that audit a product/codebase and produce a unified, prioritized launch-readiness ticket board (a git-native Jira). Use whenever the user says "war room", "gọi war room", "bật mode CTO/startup team", asks to audit-and-finish a product with a full org, get launch-ready, or spawn many role-based sub-agents that coordinate through tickets. Adaptable per project.
argument-hint: "[audit|resume|status] [notes to focus the audit]"
metadata:
  author: claude
  version: "1.0.0"
---

# War Room — AI startup org that audits & finishes a product

Stand up a five-lead C-suite plus teams, run them as sub-agents to audit the
product across every dimension, and materialize the result into a **file-based
ticket system** (a lightweight git-native Jira) with a **launch-readiness
verdict, P0 blockers, a critical path, and a Sprint 0**. Then execute the
safe, high-value tickets. Requires multi-agent orchestration (the `Workflow`
tool) — this skill's instructions authorize that call.

## When to use
- "gọi war room" / "war room" / "bật mode CTO, dev team, startup team".
- "audit và hoàn thiện sản phẩm này, ready để chạy sớm nhất".
- Any request to spawn role-based leads (CEO/CTO/CMO/COO/CPO…), each managing a
  team, coordinating through a ticket/task system.

## The org (default — adapt per project)
| Lead | Team | Owns |
|------|------|------|
| **CEO** | Strategy & BizDev | prioritization, GTM, positioning, go/no-go, existential risk |
| **CTO** | Engineering (BE/FE/DevOps/QA) | architecture, security, reliability, data model, tests, CI/CD, deploy |
| **CPO** | Product & Design | core flows, onboarding, UX, i18n, conversion, honesty of the product |
| **CMO** | Growth, Content & SEO | funnel, SEO, channels, brand/trust, compliance-safe acquisition |
| **COO** | Ops, Legal & Finance | compliance/legal, payments, KYC/AML, support, launch checklist |

Add/remove leads to fit the domain (e.g. add a **CISO** for a security product,
a **Chief Medical Officer** for health, a **Head of Data** for an ML product).

## How to run — 5 steps

### 1. Scaffold the ticket system (once per project)
Create a `warroom/` dir in the target repo and copy the templates from
`/home/ubuntu/brain/warroom/templates/`:
- `warroom/README.md` ← `README.md` (how the system works)
- `warroom/build-board.mjs` ← `build-board.mjs` (renders BOARD.md)
- `warroom/board.json` ← `board.seed.json` (source of truth; fill `org`)

`board.json` is the source of truth; `BOARD.md` is generated. Ticket lifecycle:
`backlog → todo → in_progress → review → done`. Priority P0 (launch blocker) →
P3. Effort S/M/L/XL. Ticket id = `<ROLE>-NNN`. Cross-team talk lives in each
ticket's `comments[]`.

### 2. Build the audit CONTEXT (grounding)
Before running the workflow, assemble a tight CONTEXT string describing the
actual product: what it is, stack, what's built, known gaps, the north
star/strategy, live URLs, repo path, and any hard constraints (legal, market,
platform). Pull from the repo (README/docs), the memory/brain, and recent
research. **A grounded CONTEXT is the single biggest quality lever** — agents
that get it produce real findings, not generic ones.

### 3. Run the war-room workflow
Use `/home/ubuntu/brain/warroom/templates/war-room-workflow.js` as the Workflow script. Edit the `CONTEXT`
and `LEADS` constants for this project, then invoke:
`Workflow({ script: <contents of war-room-workflow.js with CONTEXT/LEADS filled> })`
It runs three phases: **C-Suite Audit** (5 leads audit in parallel) → **Team
Deep-Dive** (each lead's specialists expand P0/P1 tickets into execution-ready
specs) → **Synthesize** (a Chief-of-Staff dedupes into one board + readiness +
critical path + Sprint 0). It returns `{ org, synthesis }`.

### 4. Materialize → board.json → BOARD.md → commit
Write the synthesis into `warroom/board.json` (normalize `role` to CEO/CTO/CPO/
CMO/COO; set every ticket `status:"backlog"`, add `comments:[]`), then
`node warroom/build-board.mjs`, then commit. See
`/home/ubuntu/brain/warroom/templates/materialize.mjs` for a ready-made script
(reads the workflow result JSON, writes board.json).

### 5. Present + execute
Show the user the **verdict, P0 blockers, critical path, Sprint 0**. Then offer
to execute — start with the **safe, market/decision-agnostic P0s** (security,
honesty, data-model, CI, dead-link/placeholder removal). Flag human-gated items
(sign a contract, legal sign-off, real money/market decisions) for the founder.
As you complete tickets, update `status` in board.json + append to `comments[]`,
rebuild, and commit — the board is the living source of truth across sessions.

## Resume / status
- **status**: read `warroom/BOARD.md` (or board.json) and summarize open P0s +
  what's in_progress.
- **resume**: pick the next unblocked P0/P1 ticket (deps all `done`), implement
  it, mark it done with a comment, rebuild, commit. Repeat.
- A stopped workflow can be resumed: `Workflow({scriptPath, resumeFromRunId})`
  (completed agents return cached — pass `args` again so the script gets them).

## Adapt & upgrade (per project + over time)
- **Per project**: change the LEADS roster, rewrite CONTEXT, add domain phases
  (e.g. a "Security Audit" phase), tune ticket count. Keep the ticket-system
  templates as-is (they're generic).
- **Upgrade the method**: when a run teaches you something (a better prompt, a
  new lead, a sharper readiness rubric), edit this SKILL.md and the templates so
  every future war room inherits it. Record notable per-project adaptations as a
  memory in that project's brain and link back here.
- **Honesty rule**: the audit must be brutally honest — surface fake/simulated
  parts, security holes, and compliance traps even when they contradict the
  founder's stated plan. A flattering audit is worthless.

## Canonical home & files
The methodology + templates live in the shared brain: **`/home/ubuntu/brain/warroom/`**
(this skill is just the trigger; read/edit/upgrade there).
- `/home/ubuntu/brain/warroom/METHODOLOGY.md` — full methodology (this doc's source).
- `/home/ubuntu/brain/warroom/templates/README.md` — ticket-system doc (copy into repo `warroom/`).
- `/home/ubuntu/brain/warroom/templates/build-board.mjs` — board renderer (copy into `warroom/`).
- `/home/ubuntu/brain/warroom/templates/board.seed.json` — empty board scaffold (copy into `warroom/`).
- `/home/ubuntu/brain/warroom/templates/war-room-workflow.js` — the 3-phase orchestration script (fill CONTEXT/LEADS).
- `/home/ubuntu/brain/warroom/templates/materialize.mjs` — turns the workflow result into board.json.