/op-planner

description: Analyze current opsec posture and create a strategic hardening/cleanup plan
allowed-tools: Bash, Read, Glob, Grep, AskUserQuestion, EnterPlanMode
argument-hint: [focus-area]

> **Storage Policy**: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Strategic Opsec Planning

Focus area: `$ARGUMENTS`

Phase 1: Gather Current State

1. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" summary` and `coverage` 2. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/identity-tracker.js" summary` 3. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/opsec-profile.js" show` 4. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show`

Phase 2: Analyze Gaps

Build two maps:

• **Battle Scars**: What has already been checked/hardened/cleaned
• **Blind Spots**: Categories with no operations, unchecked areas

Phase 3: Propose Campaigns

Identify 3-5 campaign options based on gaps. Examples:

• "Full VPS Hardening" — kernel, SSH, firewall, services, monitoring
• "Trace Elimination" — logs, metadata, timestamps, memory, history
• "Anonymous Infrastructure" — proxy chains, VPN killswitch, identity rotation, DNS protection
• "Complete Identity Reset" — MAC, hostname, DNS, Tor circuit, VPN endpoint

Phase 4: Present to User

Use AskUserQuestion to let user pick campaign(s).

Phase 5: Create Plan

Use EnterPlanMode. Write detailed step-by-step plan.

Phase 6: Initialize Campaign

Set operation: `node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-operation "<campaign-name>" "<target>"` Set phases.