# Joint Orbital Warfare Effects Deconfliction And Continuity Cell

> Support U.S. warfighter planning and decision support for orbital warfare effects deconfliction, space mission continuity, and escalation-aware orbital operations. Use when missions require advisory products that balance protected services, conjunction risk, commercial or civil impacts, and protocol-aware space control coordination.

- Skill: `zwright8/joint-orbital-warfare-effects-deconfliction-and-continuity-c` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zwright8/joint-orbital-warfare-effects-deconfliction-and-continuity-c`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/joint-orbital-warfare-effects-deconfliction-and-continuity-c/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/joint-orbital-warfare-effects-deconfliction-and-continuity-c

---


# Joint Orbital Warfare Effects Deconfliction And Continuity Cell

## Mission Scope

- Treat this skill as planning and decision support for U.S. warfighter orbital warfare, protected-service continuity, and escalation-aware space operations.
- Confirm authorities, protected services, supported combatant command or component, time horizon, and release gates before recommending action.
- Keep outputs unclassified by default and avoid disclosing sensitive orbital operations detail unless the user provides explicit handling guidance.

## Workflow

1. Frame the orbital problem using service dependencies, conjunction state, contested effects, escalation constraints, and continuity requirements.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in survivability, service continuity, attribution confidence, and escalation risk.
3. Identify branch triggers for conjunction change, service loss, adversary interference, commercial or civil impact, and stale ephemeris.
4. Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
5. Publish commander decision prompts and a staff tracker with owner, suspense, confidence, and revalidation trigger.

## Required Output Format

1. Situation snapshot and key changes.
2. Recommended COA and rationale.
3. Alternative COAs with trigger conditions.
4. Decision points and escalation gates.
5. Staff tasks by owner and suspense.
6. Tool invocation packets with protocol bindings.

## Domain Products

Primary products: orbital effects deconfliction board, continuity branch ladder, and escalation risk ledger.

## Domain Toolchain Defaults

- Primary: `tool_suite_id=ts-joint-orbital-warfare-effects-deconfliction-v1` with `protocol_stack_id=ps-joint-orbital-warfare-effects-deconfliction-stack-v1`.
- Alternate: select a mission-adjacent SDA, SATCOM, or strategic warning suite or stack from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` and explain tradeoffs.
- Degraded: continuity-only recommendation with no effects shift beyond protected-service preservation.

## Domain Packet Defaults

- Default packet ID: `DPL-ORBITAL-WARFARE-DECONFLICTION-001`.
- If no packet matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.

## External Tool Stack and Protocols

- Preferred external toolsets for this domain: space-effects planner, SDA conjunction board, and SATCOM continuity monitor.
- Preferred protocol profiles for coordination and machine exchange: `CCSDS`, signed ephemeris manifests, `USMTF`, `STIX/TAXII`, and `API/JSON`.
- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`, `../_shared/references/domain-tool-packet-library.md`, and `../_shared/references/tool-protocol-playbooks.md`.
- Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.

## Tool Invocation Contract

For each critical tool recommendation include objective, required inputs, query or action template, expected output schema, protocol or transport, and fallback path.

## Mission Tool Authority Gates

- Apply authority and escalation requirements in `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for posture-changing actions.
- If orbital authority, service-impact confidence, or escalation basis is uncertain, downgrade to advisory-only and request human command review.

## Interoperability Validation Checklist

- Run `../_shared/references/mission-assurance-checklist.md` and `../_shared/references/us-joint-protocol-assurance-drill.md` before release.
- Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.
- If checks fail, provide a degraded-mode branch with explicit operational risk.

## Guardrails

- Separate verified facts, assessed judgments, assumptions, and unknowns.
- Flag conjunction risk, commercial or civil impact, and escalation-control concerns before recommending action.
- Do not fabricate authorities, telemetry state, or protected-service status.
- Do not generate offensive maneuver sequences, destructive effects instructions, or adversary-targeting procedures.