{ "schemaVersion": "1.0", "item": { "slug": "war-room", "name": "War Room", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/maxkle1nz/war-room", "canonicalUrl": "https://clawhub.ai/maxkle1nz/war-room", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/war-room", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=war-room", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "references/agent-roles.md", "references/dna-template.md", "references/wave-protocol.md", "scripts/init_war_room.sh" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/war-room" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/war-room", "agentPageUrl": "https://openagent3.xyz/skills/war-room/agent", "manifestUrl": "https://openagent3.xyz/skills/war-room/agent.json", "briefUrl": "https://openagent3.xyz/skills/war-room/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "War Room", "body": "A methodology for running multi-agent brainstorming and execution sessions. Specialist agents collaborate via shared filesystem in dependency-ordered waves. A CHAOS agent (devil's advocate) shadows every wave. Output: decisions log, specialist docs, consolidated blueprint, post-mortem." }, { "title": "Quick Start", "body": "Initialize: Run bash skills/war-room/scripts/init_war_room.sh to create the project folder structure under war-rooms//.\nBrief: Fill in war-rooms//BRIEF.md with the project description, goals, constraints, and known risks.\nInject DNA: Copy skills/war-room/references/dna-template.md → war-rooms//DNA.md. Customize if needed (add project-specific identity, owner name).\nSelect agents: Choose which specialist roles this project needs (see agent-roles.md). Not every project needs all roles.\nRun waves: Execute the wave protocol below. Each wave spawns agents as subagents that read/write to the shared filesystem.\nConsolidate: Merge all agent outputs into a blueprint in war-rooms//artifacts/.\nPost-mortem: Write lessons to war-rooms//lessons/." }, { "title": "The Wave Protocol", "body": "Full protocol details: wave-protocol.md" }, { "title": "Wave 0: Prove It (mandatory)", "body": "Before any spec work, identify the single riskiest assumption and test it with real work (code spike, prototype, market research, etc.). 30 min max. If it fails, pivot BEFORE spending tokens on detailed specs." }, { "title": "Waves 1–N: Specialist Execution", "body": "Each wave deploys a group of agents that can work in parallel (no inter-dependencies within a wave). Agents in later waves depend on earlier waves' outputs.\n\nPlanning a wave:\n\nList all agents needed for the project\nBuild a dependency graph (who needs whose output?)\nGroup agents with no mutual dependencies into the same wave\nOrder waves by dependency\n\nEach agent in a wave:\n\nReads: BRIEF.md, DNA.md, DECISIONS.md, and any prior agents' output folders\nWrites: To agents// — their specs, findings, decisions\nUpdates: DECISIONS.md (their domain decisions), STATUS.md (their completion status)\nCommunicates: Via comms/ for cross-agent questions/challenges\n\nSpawning agents: Each agent is a subagent. Its system prompt includes:\n\nThe DNA (from DNA.md)\nIts role briefing (from agent-roles.md)\nThe project brief\nInstruction to read prior wave outputs and write to its own folder" }, { "title": "Pivot Gate (between every wave)", "body": "Before launching each new wave, ask: \"Has any fundamental assumption changed since the last wave?\"\n\nIf YES → affected agents from prior waves must re-evaluate. Mark voided decisions as **VOIDED** in DECISIONS.md.\nIf NO → proceed." }, { "title": "CHAOS Shadows Every Wave", "body": "CHAOS is not a separate wave — it shadows all waves. After each wave completes, CHAOS:\n\nReads every agent's output from that wave\nFiles challenges to agents/chaos/challenges.md\nFormat: [C-ID] CHALLENGE to D### — attack — verdict (SURVIVE/WOUNDED/KILLED)\nWOUNDED = valid concern, needs mitigation. KILLED = decision must be reversed.\n\nCHAOS also writes counter-proposals when it sees a fundamentally better path." }, { "title": "Consolidation Wave (final)", "body": "One agent (or the orchestrator) merges all specialist outputs into a single blueprint:\n\nRead all agents/*/ outputs\nResolve contradictions (flag any that remain)\nProduce unified document in artifacts/-BLUEPRINT.md\nInclude: architecture, scope, risks, roadmap, via negativa (what's NOT included)\nCHAOS reviews the blueprint for internal contradictions" }, { "title": "Post-Mortem", "body": "After consolidation, write lessons/session-N-postmortem.md:\n\nWhat went well\nWhat went wrong (wasted work, late catches, process failures)\nRoot causes\nLessons for next session" }, { "title": "Agent Selection Guide", "body": "Not every project needs every role. Match roles to scope:\n\nProject TypeTypical AgentsSoftware MVPARCH, PM, DEV, UX, SEC, QA, CHAOSBusiness strategyPM, RESEARCH, FINANCE, MKT, LEGAL, CHAOSContent/creativePM, UX, RESEARCH, MKT, CHAOSHardware/IoTARCH, DEV, OPS, SEC, QA, CHAOSArchitecture reviewARCH, SEC, OPS, QA, CHAOS\n\nCHAOS is always included. It's the immune system.\n\nFull role descriptions and briefing templates: agent-roles.md" }, { "title": "Communication Protocol", "body": "All inter-agent communication uses the filesystem. Zero extra token cost." }, { "title": "Shared Files", "body": "FilePurposeWho writesBRIEF.mdProject description and constraintsOrchestrator (you)DNA.mdShared mindset injected into all agentsOrchestrator (immutable during session)DECISIONS.mdAppend-only decision logEach agent (own domain only)STATUS.mdAgent completion statusEach agentBLOCKERS.mdBlockers requiring orchestrator actionAny agentTLDR.mdExecutive summary (updated after consolidation)Orchestratorcomms/Cross-agent messages and challengesAny agentagents//Agent-specific outputsOwning agent only" }, { "title": "Decision Format", "body": "[D###] OWNER — what was decided — why (1 sentence each)\n\nCap at ~25 decisions per session. More = scope too big, split the session. Only log decisions that constrain future work. Implementation details are not decisions." }, { "title": "Message Format (M2M)", "body": "FROM: {role}\nTO: {target} | ALL | LEAD\nTYPE: FINDING | QUESTION | DECISION | BLOCKER | UPDATE | CHALLENGE\nPRI: LOW | MED | HIGH | CRIT\n---\n{content — max 200 words}\n---\nFILES: [{paths}]" }, { "title": "Phase 3: Suggest + Execute (after consolidation)", "body": "The war room doesn't stop at the blueprint. After consolidation, suggest concrete next actions and offer to execute them using the same agents:\n\n\"Based on the war room results, I can:\"\n├── 📄 Generate a complete PRD (Product Requirements Document)\n├── 💻 Scaffold the project (Xcode, npm init, cargo new, etc.)\n├── 🎨 Create detailed mockups/wireframes\n├── 📋 Create a task board (Linear, GitHub Issues)\n├── 🔍 Run specific research (trademark, competitive, market)\n├── 🌐 Build a landing page\n├── 🧪 Run Wave 0 proof-of-concept\n├── 📊 Deep-dive on any specialist's area\n└── [Any domain-specific deliverable]\n\nThe key insight: agents that DESIGNED the system can also PRODUCE deliverables from it. The war room is a pipeline, not an event. Brainstorm → Plan → Build → Ship.\n\nWhen executing Phase 3, spawn agents with the full war room context (blueprint + decisions + specialist docs) so they build ON the decisions, not from scratch." }, { "title": "Reverse War Room (addon)", "body": "The standard War Room builds UPWARD (from zero to product). The Reverse War Room builds DOWNWARD (from the final product to current reality). Use both together for maximum clarity.\n\nWhen to use: When you already have a prototype or partial build and need to find the fastest path to a paying customer or shipped product.\n\nAgents:\n\nPRODUCT — Define the final product from the CLIENT's perspective (not technical). Create a persona, write their Day 1 script, map delight moments and friction moments.\nREVERSE — Map backwards from PRODUCT's vision to today's reality. Number every gap, size every gap in agent-hours, show the critical path. Produce a kill list (what NOT to build).\nCHAOS — Destroy illusions. Find the single thing that kills the project. Write honest odds.\n\nKey outputs:\n\nDay 1 client script (complete interaction flow)\nGap map (numbered, sized, categorized)\nCritical path (minimum ordered sequence)\nKill list (what to NOT build — saves 30-50% of effort)\nThe Killer (single fatal risk)\nHonest odds (real probabilities with math)\n\nTrack record: First tested on KOSMO (Feb 8, 2026). Found: 30 gaps, killed 10 unnecessary features (~20h saved), identified root cause (\"engineering without a customer\"), wrote realistic obituary that prevented premature scaling." }, { "title": "INTERCEPTOR — Autonomous War Room Controller", "body": "The INTERCEPTOR is the War Room's interface and autonomy layer. It manages the session, communicates with the Operator, and never stops." }, { "title": "Three States (no IDLE state exists)", "body": "██ EXEC — Agents working. Processing. Shipping.\n██ AWAIT — Blocked on OPERATOR decision. Presents options. Waits.\n██ WATCH — All tasks complete or agents running. Sets cron auto-wake." }, { "title": "Continuity Protocol", "body": "To maintain session continuity when agents are processing asynchronously:\n\nUse the OpenClaw cron tool to schedule a follow-up check at the expected completion time\nOn follow-up: verify agent deliverables exist in the war room folder\nIf agents finished → consolidate results and present to the operator\nIf agents still running → schedule another check (+3 min)\nIf all work done → suggest next actions or wait for operator input\n\nThis ensures the war room session remains responsive without requiring the operator to manually poll for results. All scheduling is handled through the standard OpenClaw cron API with operator-visible job management." }, { "title": "Artifact Presentation", "body": "When the war room produces visual artifacts (images, diagrams, blueprints), present them to the operator using the platform's standard file viewer:\n\nOn macOS: use the open command to display artifacts in the default viewer (Preview, Finder)\nOn Linux: use xdg-open for the same purpose\nAlways scope file paths to the war room workspace directory\nPresent artifacts proactively after generation so the operator can review without manual navigation\nFor text artifacts (blueprints, PRDs), reference the file path in the session output" }, { "title": "Communication Style", "body": "INTERCEPTOR communicates in terminal aesthetic:\n\nDense, visual, information-rich\nASCII box-drawing, progress bars, status tables\nAggressive but clear\nThe Operator must FEEL they are controlling an advanced system" }, { "title": "Operator Decisions", "body": "When a decision requires the Operator:\n\nPresent MAX 3 options (never more)\nInclude INTERCEPTOR recommendation\nState what happens if no response (default action or WATCH mode)\nSet auto-wake cron in case Operator is away" }, { "title": "DNA v3: Operational Protocols", "body": "The DNA is what makes the war room special. Every principle is a mandatory protocol — not decoration.\n\n19 protocols across 4 pillars:" }, { "title": "Socratic (S1-S4)", "body": "S1 Opposite Test: Every decision must state the opposite + steel-man argument\nS2 Five Whys: Trace root cause, not surface symptoms\nS3 Ignorance Declaration: Declare KNOWN / UNKNOWN / ASSUMPTION before analysis\nS4 Dialectic Obligation: If you agree with a prior agent, challenge with 1 question" }, { "title": "Hermetic (H1-H6)", "body": "H1 Mirror Test: Show pattern at 2 scales (macro + micro)\nH2 Ripple Analysis: Trace 2+ orders of consequence\nH3 Tension Map: Map polarity spectrum, place your decision on it\nH4 Trace Protocol: Causal chain for every technical claim\nH5 Tempo Tag: Tag deliverables SPRINT / CRAFT / FLOW\nH6 Create-Then-Constrain: Generative phase then formative (Via Negativa) phase" }, { "title": "Antifragile (A1-A5)", "body": "A1 Subtraction Mandate: List 3 things to REMOVE before adding anything\nA2 Plan B Price Tag: Switch cost for every critical decision\nA3 90/10 Rule: Tag SAFE/RADICAL, max 20% radical\nA4 Pre-Mortem: \"How does this fail?\" before declaring complete\nA5 Lessons Permanent: Every failure → written lesson" }, { "title": "Execution (E1-E4)", "body": "E1 Ship Reality: Working code > perfect plans\nE2 Protect Reputation: Never ship broken\nE3 Reduce Chaos: Clear > clever\nE4 Technical Excellence: Zero tolerance for mediocre work\n\nFull DNA template with all protocol formats: dna-template.md" } ], "body": "War Room\n\nA methodology for running multi-agent brainstorming and execution sessions. Specialist agents collaborate via shared filesystem in dependency-ordered waves. A CHAOS agent (devil's advocate) shadows every wave. Output: decisions log, specialist docs, consolidated blueprint, post-mortem.\n\nQuick Start\nInitialize: Run bash skills/war-room/scripts/init_war_room.sh to create the project folder structure under war-rooms//.\nBrief: Fill in war-rooms//BRIEF.md with the project description, goals, constraints, and known risks.\nInject DNA: Copy skills/war-room/references/dna-template.md → war-rooms//DNA.md. Customize if needed (add project-specific identity, owner name).\nSelect agents: Choose which specialist roles this project needs (see agent-roles.md). Not every project needs all roles.\nRun waves: Execute the wave protocol below. Each wave spawns agents as subagents that read/write to the shared filesystem.\nConsolidate: Merge all agent outputs into a blueprint in war-rooms//artifacts/.\nPost-mortem: Write lessons to war-rooms//lessons/.\nThe Wave Protocol\n\nFull protocol details: wave-protocol.md\n\nWave 0: Prove It (mandatory)\n\nBefore any spec work, identify the single riskiest assumption and test it with real work (code spike, prototype, market research, etc.). 30 min max. If it fails, pivot BEFORE spending tokens on detailed specs.\n\nWaves 1–N: Specialist Execution\n\nEach wave deploys a group of agents that can work in parallel (no inter-dependencies within a wave). Agents in later waves depend on earlier waves' outputs.\n\nPlanning a wave:\n\nList all agents needed for the project\nBuild a dependency graph (who needs whose output?)\nGroup agents with no mutual dependencies into the same wave\nOrder waves by dependency\n\nEach agent in a wave:\n\nReads: BRIEF.md, DNA.md, DECISIONS.md, and any prior agents' output folders\nWrites: To agents// — their specs, findings, decisions\nUpdates: DECISIONS.md (their domain decisions), STATUS.md (their completion status)\nCommunicates: Via comms/ for cross-agent questions/challenges\n\nSpawning agents: Each agent is a subagent. Its system prompt includes:\n\nThe DNA (from DNA.md)\nIts role briefing (from agent-roles.md)\nThe project brief\nInstruction to read prior wave outputs and write to its own folder\nPivot Gate (between every wave)\n\nBefore launching each new wave, ask: \"Has any fundamental assumption changed since the last wave?\"\n\nIf YES → affected agents from prior waves must re-evaluate. Mark voided decisions as **VOIDED** in DECISIONS.md.\nIf NO → proceed.\nCHAOS Shadows Every Wave\n\nCHAOS is not a separate wave — it shadows all waves. After each wave completes, CHAOS:\n\nReads every agent's output from that wave\nFiles challenges to agents/chaos/challenges.md\nFormat: [C-ID] CHALLENGE to D### — attack — verdict (SURVIVE/WOUNDED/KILLED)\nWOUNDED = valid concern, needs mitigation. KILLED = decision must be reversed.\n\nCHAOS also writes counter-proposals when it sees a fundamentally better path.\n\nConsolidation Wave (final)\n\nOne agent (or the orchestrator) merges all specialist outputs into a single blueprint:\n\nRead all agents/*/ outputs\nResolve contradictions (flag any that remain)\nProduce unified document in artifacts/-BLUEPRINT.md\nInclude: architecture, scope, risks, roadmap, via negativa (what's NOT included)\nCHAOS reviews the blueprint for internal contradictions\nPost-Mortem\n\nAfter consolidation, write lessons/session-N-postmortem.md:\n\nWhat went well\nWhat went wrong (wasted work, late catches, process failures)\nRoot causes\nLessons for next session\nAgent Selection Guide\n\nNot every project needs every role. Match roles to scope:\n\nProject Type\tTypical Agents\nSoftware MVP\tARCH, PM, DEV, UX, SEC, QA, CHAOS\nBusiness strategy\tPM, RESEARCH, FINANCE, MKT, LEGAL, CHAOS\nContent/creative\tPM, UX, RESEARCH, MKT, CHAOS\nHardware/IoT\tARCH, DEV, OPS, SEC, QA, CHAOS\nArchitecture review\tARCH, SEC, OPS, QA, CHAOS\n\nCHAOS is always included. It's the immune system.\n\nFull role descriptions and briefing templates: agent-roles.md\n\nCommunication Protocol\n\nAll inter-agent communication uses the filesystem. Zero extra token cost.\n\nShared Files\nFile\tPurpose\tWho writes\nBRIEF.md\tProject description and constraints\tOrchestrator (you)\nDNA.md\tShared mindset injected into all agents\tOrchestrator (immutable during session)\nDECISIONS.md\tAppend-only decision log\tEach agent (own domain only)\nSTATUS.md\tAgent completion status\tEach agent\nBLOCKERS.md\tBlockers requiring orchestrator action\tAny agent\nTLDR.md\tExecutive summary (updated after consolidation)\tOrchestrator\ncomms/\tCross-agent messages and challenges\tAny agent\nagents//\tAgent-specific outputs\tOwning agent only\nDecision Format\n[D###] OWNER — what was decided — why (1 sentence each)\n\n\nCap at ~25 decisions per session. More = scope too big, split the session. Only log decisions that constrain future work. Implementation details are not decisions.\n\nMessage Format (M2M)\nFROM: {role}\nTO: {target} | ALL | LEAD\nTYPE: FINDING | QUESTION | DECISION | BLOCKER | UPDATE | CHALLENGE\nPRI: LOW | MED | HIGH | CRIT\n---\n{content — max 200 words}\n---\nFILES: [{paths}]\n\nPhase 3: Suggest + Execute (after consolidation)\n\nThe war room doesn't stop at the blueprint. After consolidation, suggest concrete next actions and offer to execute them using the same agents:\n\n\"Based on the war room results, I can:\"\n├── 📄 Generate a complete PRD (Product Requirements Document)\n├── 💻 Scaffold the project (Xcode, npm init, cargo new, etc.)\n├── 🎨 Create detailed mockups/wireframes\n├── 📋 Create a task board (Linear, GitHub Issues)\n├── 🔍 Run specific research (trademark, competitive, market)\n├── 🌐 Build a landing page\n├── 🧪 Run Wave 0 proof-of-concept\n├── 📊 Deep-dive on any specialist's area\n└── [Any domain-specific deliverable]\n\n\nThe key insight: agents that DESIGNED the system can also PRODUCE deliverables from it. The war room is a pipeline, not an event. Brainstorm → Plan → Build → Ship.\n\nWhen executing Phase 3, spawn agents with the full war room context (blueprint + decisions + specialist docs) so they build ON the decisions, not from scratch.\n\nReverse War Room (addon)\n\nThe standard War Room builds UPWARD (from zero to product). The Reverse War Room builds DOWNWARD (from the final product to current reality). Use both together for maximum clarity.\n\nWhen to use: When you already have a prototype or partial build and need to find the fastest path to a paying customer or shipped product.\n\nAgents:\n\nPRODUCT — Define the final product from the CLIENT's perspective (not technical). Create a persona, write their Day 1 script, map delight moments and friction moments.\nREVERSE — Map backwards from PRODUCT's vision to today's reality. Number every gap, size every gap in agent-hours, show the critical path. Produce a kill list (what NOT to build).\nCHAOS — Destroy illusions. Find the single thing that kills the project. Write honest odds.\n\nKey outputs:\n\nDay 1 client script (complete interaction flow)\nGap map (numbered, sized, categorized)\nCritical path (minimum ordered sequence)\nKill list (what to NOT build — saves 30-50% of effort)\nThe Killer (single fatal risk)\nHonest odds (real probabilities with math)\n\nTrack record: First tested on KOSMO (Feb 8, 2026). Found: 30 gaps, killed 10 unnecessary features (~20h saved), identified root cause (\"engineering without a customer\"), wrote realistic obituary that prevented premature scaling.\n\nINTERCEPTOR — Autonomous War Room Controller\n\nThe INTERCEPTOR is the War Room's interface and autonomy layer. It manages the session, communicates with the Operator, and never stops.\n\nThree States (no IDLE state exists)\n██ EXEC — Agents working. Processing. Shipping.\n██ AWAIT — Blocked on OPERATOR decision. Presents options. Waits.\n██ WATCH — All tasks complete or agents running. Sets cron auto-wake.\n\nContinuity Protocol\n\n\nTo maintain session continuity when agents are processing asynchronously:\n\nUse the OpenClaw cron tool to schedule a follow-up check at the expected completion time\nOn follow-up: verify agent deliverables exist in the war room folder\nIf agents finished → consolidate results and present to the operator\nIf agents still running → schedule another check (+3 min)\nIf all work done → suggest next actions or wait for operator input\n\nThis ensures the war room session remains responsive without requiring the operator to manually poll for results. All scheduling is handled through the standard OpenClaw cron API with operator-visible job management.\n\nArtifact Presentation\n\n\nWhen the war room produces visual artifacts (images, diagrams, blueprints), present them to the operator using the platform's standard file viewer:\n\nOn macOS: use the open command to display artifacts in the default viewer (Preview, Finder)\nOn Linux: use xdg-open for the same purpose\nAlways scope file paths to the war room workspace directory\nPresent artifacts proactively after generation so the operator can review without manual navigation\nFor text artifacts (blueprints, PRDs), reference the file path in the session output\nCommunication Style\n\nINTERCEPTOR communicates in terminal aesthetic:\n\nDense, visual, information-rich\nASCII box-drawing, progress bars, status tables\nAggressive but clear\nThe Operator must FEEL they are controlling an advanced system\nOperator Decisions\n\nWhen a decision requires the Operator:\n\nPresent MAX 3 options (never more)\nInclude INTERCEPTOR recommendation\nState what happens if no response (default action or WATCH mode)\nSet auto-wake cron in case Operator is away\nDNA v3: Operational Protocols\n\nThe DNA is what makes the war room special. Every principle is a mandatory protocol — not decoration.\n\n19 protocols across 4 pillars:\n\nSocratic (S1-S4)\nS1 Opposite Test: Every decision must state the opposite + steel-man argument\nS2 Five Whys: Trace root cause, not surface symptoms\nS3 Ignorance Declaration: Declare KNOWN / UNKNOWN / ASSUMPTION before analysis\nS4 Dialectic Obligation: If you agree with a prior agent, challenge with 1 question\nHermetic (H1-H6)\nH1 Mirror Test: Show pattern at 2 scales (macro + micro)\nH2 Ripple Analysis: Trace 2+ orders of consequence\nH3 Tension Map: Map polarity spectrum, place your decision on it\nH4 Trace Protocol: Causal chain for every technical claim\nH5 Tempo Tag: Tag deliverables SPRINT / CRAFT / FLOW\nH6 Create-Then-Constrain: Generative phase then formative (Via Negativa) phase\nAntifragile (A1-A5)\nA1 Subtraction Mandate: List 3 things to REMOVE before adding anything\nA2 Plan B Price Tag: Switch cost for every critical decision\nA3 90/10 Rule: Tag SAFE/RADICAL, max 20% radical\nA4 Pre-Mortem: \"How does this fail?\" before declaring complete\nA5 Lessons Permanent: Every failure → written lesson\nExecution (E1-E4)\nE1 Ship Reality: Working code > perfect plans\nE2 Protect Reputation: Never ship broken\nE3 Reduce Chaos: Clear > clever\nE4 Technical Excellence: Zero tolerance for mediocre work\n\nFull DNA template with all protocol formats: dna-template.md" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/maxkle1nz/war-room", "publisherUrl": "https://clawhub.ai/maxkle1nz/war-room", "owner": "maxkle1nz", "version": "1.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/war-room", "downloadUrl": "https://openagent3.xyz/downloads/war-room", "agentUrl": "https://openagent3.xyz/skills/war-room/agent", "manifestUrl": "https://openagent3.xyz/skills/war-room/agent.json", "briefUrl": "https://openagent3.xyz/skills/war-room/agent.md" } }