← ClaudeAtlas

mission-risk-decision-supportlisted

Quantify and communicate mission risk for commander decisions. Use when comparing options under uncertainty and documenting risk acceptance with controls.
zwright8/OpenClaw-Code · ★ 0 · DevOps & Infrastructure · score 60
Install: claude install-skill zwright8/OpenClaw-Code
# Mission Risk Decision Support ## Mission Scope - Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain. - Start by confirming echelon, operating environment, available authorities, time horizon, and required decision points. - Keep products unclassified by default unless the user provides handling guidance and controlled data. ## Workflow 1. Frame the mission problem using these core inputs: COAs, threat likelihood/severity, control measures, commander risk tolerance. 2. Identify assumptions, decision thresholds, and what intelligence or reporting would invalidate the current plan. 3. Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk. 4. Integrate dependencies across joint functions: command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information. 5. Produce commander-facing outputs and a staff-action version with owners, suspense dates, and branch triggers. ## Required Output Format Deliver results in this order: 1. Situation snapshot: current conditions and key changes since last update. 2. Recommended option: one clearly stated recommendation and rationale. 3. Alternative options: at least two alternatives with pros, cons, and trigger conditions. 4. Decision points: what must be decided now, later, or pre-delegated. 5. Staff tasking: who does what by when. ## Domain Products Primary products for thi