War Room Checkpoint logo

War Room Checkpoint

Community
athola
war-room-checkpoint

Assesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.

Overview

Publisherathola
Repositoryclaude-night-market
Skill namewar-room-checkpoint
Stars
343
Forks
37
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by athola on GitHub. Read the source before you install it.

Installation

Install the War Room Checkpoint AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/athola/claude-night-market/tree/master/plugins/attune/skills/war-room-checkpoint
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/athola/claude-night-market.git /tmp/claude-night-market
mkdir -p .claude/skills
cp -r /tmp/claude-night-market/plugins/attune/skills/war-room-checkpoint .claude/skills/war-room-checkpoint
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable War Room Checkpoint in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads War Room Checkpoint on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so War Room Checkpoint is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

War Room Checkpoint Skill

Lightweight inline assessment for determining whether a decision point within a command warrants War Room escalation.

Verification

Run make attune-test from the repository root to verify checkpoint logic still works after changes.

Purpose

This skill is not invoked directly by users. It is called by other commands (e.g., /do-issue, /pr-review) at critical decision points to:

  1. Calculate Reversibility Score (RS) for the current context
  2. Determine if full War Room deliberation is needed
  3. Return either a quick recommendation (express) or escalate to full War Room

When Commands Should Invoke This

CommandTrigger Conditions
/do-issue3+ issues, dependency conflicts, overlapping files
/pr-review>3 blocking issues, architecture changes, ADR violations
/architecture-reviewADR violations, high coupling, boundary violations
/fix-prMajor scope, conflicting reviewer feedback

When NOT To Use

SituationUse instead
A user asks for deliberation directlySkill(attune:war-room)
The decision is cheap to reverse (high RS)Proceed without a checkpoint
A panel already ruled on this decisionThe prior verdict

This skill decides whether deliberation is warranted and returns fast when it is not. A command that checkpoints every decision pays the scoring cost to be told to proceed almost every time, and re-checkpointing a settled call re-litigates it.

Invocation Pattern

markdown
Skill(attune:war-room-checkpoint) with context:
  - source_command: "{calling_command}"
  - decision_needed: "{human_readable_question}"
  - files_affected: [{list_of_files}]
  - issues_involved: [{issue_numbers}] (if applicable)
  - blocking_items: [{type, description}] (if applicable)
  - conflict_description: "{summary}" (if applicable)
  - profile: "default" | "startup" | "regulated" | "fast" | "cautious"

Checkpoint Flow

Step 1: Context Analysis

Analyze the provided context to extract:

  • Scope of change (files, modules, services affected)
  • Stakeholders impacted
  • Conflict indicators
  • Time pressure signals

Step 2: Reversibility Assessment

Calculate RS using the 5-dimension framework:

DimensionAssessment Question
Reversal CostHow hard to undo this decision?
Time Lock-InDoes this crystallize immediately?
Blast RadiusHow many components/people affected?
Information LossDoes this close off future options?
Reputation ImpactIs this visible externally?

Score each 1-5, calculate RS = Sum / 25.

Step 3: Mode Selection

Apply profile thresholds to determine mode:

if RS <= profile.express_ceiling:
    mode = "express"
elif RS <= profile.lightweight_ceiling:
    mode = "lightweight"
elif RS <= profile.full_council_ceiling:
    mode = "full_council"
else:
    mode = "delphi"

Step 4: Response Generation

Express Mode (RS <= threshold)

Return immediately with recommendation:

yaml
response:
  should_escalate: false
  selected_mode: "express"
  reversibility_score: {rs}
  decision_type: "Type 2"
  recommendation: "{quick_recommendation}"
  rationale: "{brief_explanation}"
  confidence: 0.9
  requires_user_confirmation: false
Escalate Mode (RS > threshold)

Invoke full War Room and return results:

yaml
response:
  should_escalate: true
  selected_mode: "{lightweight|full_council|delphi}"
  reversibility_score: {rs}
  decision_type: "{Type 1B|1A|1A+}"
  war_room_session_id: "{session_id}"
  orders: ["{order_1}", "{order_2}"]
  rationale: "{war_room_rationale}"
  confidence: {calculated_confidence}
  requires_user_confirmation: {true_if_confidence_low}

Confidence Calculation

For escalated decisions, calculate confidence for auto-continue:

confidence = 1.0
- 0.10 * dissenting_view_count
- 0.20 if voting_margin < 0.3
- 0.15 if RS > 0.80
- 0.10 if novel_domain
- 0.10 if compound_decision
+ 0.20 if unanimous (cap at 1.0)

requires_user_confirmation = (confidence <= 0.8)

Profile Thresholds

ProfileExpressLightweightFull CouncilUse Case
default0.400.600.80Balanced
startup0.550.750.90Move fast
regulated0.250.450.65Compliance
fast0.500.700.90Speed priority
cautious0.300.500.70Higher stakes

Command-Specific Adjustments

CommandAdjustmentRationale
do-issue (3+ issues)-0.10Higher risk with multiple issues
pr-review (strict mode)-0.15Strict mode = higher scrutiny
architecture-review-0.05Architecture inherently consequential

Output Format

For Calling Command

Return a structured response that the calling command can act on:

markdown
## Checkpoint Response

**Source**: {source_command}
**Decision**: {decision_needed}

### Assessment
- **RS**: {reversibility_score} ({decision_type})
- **Mode**: {selected_mode}
- **Escalated**: {yes|no}

### Recommendation
{recommendation_or_orders}

### Control Flow
- **Confidence**: {confidence}
- **Auto-continue**: {yes|no}
{user_prompt_if_needed}

Integration Notes

Calling Commands Should

  1. Check checkpoint response's requires_user_confirmation
  2. If true: present confirmation prompt and wait
  3. If false: continue with orders or recommendation
  4. Log checkpoint to audit trail

Failure Handling

If checkpoint invocation fails:

  • Log warning with context
  • Continue command execution without checkpoint
  • Do NOT block the user's workflow

Audit Trail

Checkpoints are logged to:

~/.claude/memory-palace/strategeion/checkpoints/{date}/{checkpoint-id}.json

Each file contains a CheckpointEntry with: checkpoint_id, session_id, phase, action, reversibility_score, dimensions, confidence, files_affected, and requires_user_confirmation.

After a war room session completes and persist_session() is called, an audit report is written automatically to:

~/.claude/memory-palace/strategeion/war-table/{session-id}/audit-report.json

The report consolidates: all checkpoints for the session, the expert panel, voting summary with unanimity score, escalation history, final decision and rationale, and a Merkle-DAG integrity verification block. The verification recomputes every node hash against the stored values so any tampering with deliberation content is detectable.

Use AuditTrailManager from scripts.war_room.audit_trail to query checkpoints or generate reports programmatically:

python
from scripts.war_room.audit_trail import AuditTrailManager
manager = AuditTrailManager()
checkpoints = manager.get_checkpoints("war-room-20260303-100000")
audited = manager.list_audited_sessions()

Examples

Example 1: Low RS (Express)

Input:

yaml
source_command: "do-issue"
decision_needed: "Execution order for issues #101, #102"
issues_involved: [101, 102]
files_affected: ["src/utils/helper.py", "tests/test_helper.py"]

Assessment:

  • Reversal Cost: 1 (can revert commits)
  • Time Lock-In: 1 (no deadline)
  • Blast Radius: 1 (single utility module)
  • Information Loss: 1 (all options preserved)
  • Reputation Impact: 1 (internal)

RS: 0.20 (Type 2)

Response:

yaml
should_escalate: false
selected_mode: "express"
recommendation: "Execute in parallel - no dependencies detected"
confidence: 0.95
requires_user_confirmation: false

Example 2: High RS (Escalate)

Input:

yaml
source_command: "pr-review"
decision_needed: "Review verdict for PR #456"
blocking_items:
  - {type: "architecture", description: "New service without ADR"}
  - {type: "breaking", description: "API contract change"}
  - {type: "security", description: "Auth flow modification"}
  - {type: "scope", description: "Unrelated payment refactor"}
files_affected: ["src/auth/", "src/api/", "src/payment/", "src/services/new/"]

Assessment:

  • Reversal Cost: 4 (multi-service impact)
  • Time Lock-In: 3 (PR deadline pressure)
  • Blast Radius: 4 (cross-team impact)
  • Information Loss: 3 (some paths closing)
  • Reputation Impact: 2 (internal review)

RS: 0.64 (Type 1A)

Response:

yaml
should_escalate: true
selected_mode: "full_council"
war_room_session_id: "war-room-20260125-143025"
orders:
  - "Split PR: auth changes separate from payment refactor"
  - "Require ADR for new service before merge"
  - "API change: add migration path, not blocking"
confidence: 0.75
requires_user_confirmation: true

Related Skills

  • Skill(attune:war-room) - Full War Room deliberation
  • Skill(attune:war-room)/modules/reversibility-assessment.md - RS framework

Related Commands

  • /attune:war-room - Standalone War Room invocation
  • /do-issue - Issue implementation (uses this checkpoint)
  • /pr-review - PR review (uses this checkpoint)
  • /architecture-review - Architecture review (uses this checkpoint)
  • /fix-pr - PR fix (uses this checkpoint)

Exit Criteria

  • A structured checkpoint response is returned with all required fields: reversibility_score (0.0-1.0), selected_mode (express / lightweight / full_council / delphi), should_escalate (boolean), and recommendation or orders.
  • Any response with reversibility_score > profile threshold has should_escalate: true and triggers the full War Room via Skill(attune:war-room) before returning.
  • Any response with confidence <= 0.8 sets requires_user_confirmation: true and presents a confirmation prompt to the user rather than auto-continuing.
  • The checkpoint is logged to ~/.claude/memory-palace/strategeion/checkpoints/{date}/{checkpoint-id}.json; if this write fails, the calling command proceeds and logs a warning rather than blocking the workflow.

Frequently asked questions

What does the War Room Checkpoint AI skill do?

Assesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.

Why use War Room Checkpoint on TypingMind?

Because you install it once and use it with any model. War Room Checkpoint is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install War Room Checkpoint in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/athola/claude-night-market/tree/master/plugins/attune/skills/war-room-checkpoint. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use War Room Checkpoint?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with War Room Checkpoint?

As many as you like. As long as a model supports skills, you can use War Room Checkpoint with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the War Room Checkpoint AI skill free?

Yes. It is published on GitHub by athola under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇