Coalition Contested Orbital Servicing and Rendezvous Safety Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm command echelon, mission phase, authorities, coalition constraints, and required commander decisions.
- Keep output unclassified by default unless handling guidance is provided.
Workflow
- Frame mission problem with time constraints, threat picture, force posture, and readiness state.
- Build one recommended COA plus at least two alternatives with explicit tradeoffs.
- Identify branch/sequel triggers, data dependencies, and command approval gates.
- Bind each critical recommendation to external tools, protocol stack, and degraded-mode fallback.
- Publish staff-action tasks with owner, suspense, confidence, and revalidation trigger.
Required Output Format
- Situation snapshot and key changes.
- Recommended COA and rationale.
- Alternative COAs with triggers.
- Decision points and escalation gates.
- Staff task tracker with owners/suspense.
- Tool invocation packets and protocol bindings.
Domain Products
Primary products for this skill: mission-risk brief, decision matrix, and branch trigger map.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-coalition-orbital-servicing-rendezvous-safety-v1 with protocol_stack_id=ps-coalition-orbital-servicing-rendezvous-safety-stack-v1.
- Alternate: choose a mission-adjacent suite from
../_shared/references/warfighter-external-tool-and-protocol-catalog.md and a corresponding stack.
- Degraded: authenticated voice/readback plus UTC acknowledgment ledger and manual sync board.
Domain Packet Defaults
- Default packet IDs:
DPL-ORBITAL-SERVICING-SAFETY-001, DPL-COALITION-RPO-DECONFLICTION-001.
- If no packet fully matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.
External Tool Stack and Protocols
- Use concrete suite/stack entries from
../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
- Use packet references in
../_shared/references/domain-tool-packet-library.md and playbooks in ../_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/action template, expected output schema, protocol/transport, and fallback path.
Mission Tool Authority Gates
- Apply authority and escalation requirements from
../_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 authority, legal basis, or provenance is uncertain, downgrade to advisory-only and request command decision.
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 legal, ROE, LOAC, policy, and coalition caveat constraints before recommending action.
- Do not fabricate classified sources, authorities, or approvals.
1---2name: coalition-contested-orbital-servicing-and-rendezvous-safety3description: Plan coalition orbital servicing and rendezvous safety under adversary interference, legal constraints, and collision-risk pressure.4metadata:5 source: https://skillmd.com/skills/zwright8/coalition-contested-orbital-servicing-and-rendezvous-safety6---78# Coalition Contested Orbital Servicing and Rendezvous Safety Cell910## Mission Scope1112- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.13- Confirm command echelon, mission phase, authorities, coalition constraints, and required commander decisions.14- Keep output unclassified by default unless handling guidance is provided.1516## Workflow17181. Frame mission problem with time constraints, threat picture, force posture, and readiness state.192. Build one recommended COA plus at least two alternatives with explicit tradeoffs.203. Identify branch/sequel triggers, data dependencies, and command approval gates.214. Bind each critical recommendation to external tools, protocol stack, and degraded-mode fallback.225. Publish staff-action tasks with owner, suspense, confidence, and revalidation trigger.2324## Required Output Format25261. Situation snapshot and key changes.272. Recommended COA and rationale.283. Alternative COAs with triggers.294. Decision points and escalation gates.305. Staff task tracker with owners/suspense.316. Tool invocation packets and protocol bindings.3233## Domain Products3435Primary products for this skill: mission-risk brief, decision matrix, and branch trigger map.3637## Domain Toolchain Defaults3839- Primary: `tool_suite_id=ts-coalition-orbital-servicing-rendezvous-safety-v1` with `protocol_stack_id=ps-coalition-orbital-servicing-rendezvous-safety-stack-v1`.40- Alternate: choose a mission-adjacent suite from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` and a corresponding stack.41- Degraded: authenticated voice/readback plus UTC acknowledgment ledger and manual sync board.4243## Domain Packet Defaults4445- Default packet IDs: `DPL-ORBITAL-SERVICING-SAFETY-001`, `DPL-COALITION-RPO-DECONFLICTION-001`.46- If no packet fully matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.4748## External Tool Stack and Protocols4950- Use concrete suite/stack entries from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.51- Use packet references in `../_shared/references/domain-tool-packet-library.md` and playbooks in `../_shared/references/tool-protocol-playbooks.md`.52- Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.5354## Tool Invocation Contract5556For each critical tool recommendation include: objective, required inputs, query/action template, expected output schema, protocol/transport, and fallback path.5758## Mission Tool Authority Gates5960- Apply authority and escalation requirements from `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.61- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for posture-changing actions.62- If authority, legal basis, or provenance is uncertain, downgrade to advisory-only and request command decision.6364## Interoperability Validation Checklist6566- Run `../_shared/references/mission-assurance-checklist.md` and `../_shared/references/us-joint-protocol-assurance-drill.md` before release.67- Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.68- If checks fail, provide a degraded-mode branch with explicit operational risk.6970## Guardrails7172- Separate verified facts, assessed judgments, assumptions, and unknowns.73- Flag legal, ROE, LOAC, policy, and coalition caveat constraints before recommending action.74- Do not fabricate classified sources, authorities, or approvals.