# Theater Uas Launch Site Pattern Disruption Cell

> Identify and disrupt adversary UAS launch-site patterns across the theater. Use when commanders need persistent anti-UAS campaign shaping beyond point defense.

- Skill: `zwright8/theater-uas-launch-site-pattern-disruption-cell` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/theater-uas-launch-site-pattern-disruption-cell`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/theater-uas-launch-site-pattern-disruption-cell/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/theater-uas-launch-site-pattern-disruption-cell

---


# Theater UAS Launch Site Pattern Disruption Cell

## 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 with domain indicators, commander priorities, and branch triggers.
2. Identify assumptions, decision thresholds, and invalidation signals.
3. Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
4. Integrate dependencies across C2, intelligence, fires/effects, sustainment, protection, legal constraints, and coalition interoperability.
5. Produce commander-facing outputs and a staff-action plan with owners, suspense dates, and triggers.

## Required Output Format

1. Situation snapshot.
2. Recommended option.
3. Alternative options.
4. Decision points now/next/pre-delegated.
5. Staff tasking by owner and suspense.

## Domain Products

Primary products for this skill: launch-site pattern atlas, disruption branch map, reattack prioritization matrix.

## Domain Toolchain Defaults

- Primary: `tool_suite_id=ts-air-defense-ammo-economy-v1` with `protocol_stack_id=ps-counter-uas-killchain-stack-v1`.
- Alternate: `tool_suite_id=ts-intel-fusion-v1` with `protocol_stack_id=ps-osint-info-ops-stack-v1`.
- Degraded: use authenticated voice/readback + UTC acknowledgment ledger + manual fallback board.

## External Tools and Protocol Integration

- Use baseline guidance in `../_shared/references/external-tools-protocols.md`.
- Use protocol packets in `../_shared/references/tool-protocol-playbooks.md` and `../_shared/references/domain-tool-packet-library.md`.
- Bind recommendations to concrete suite/stack entries in `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.
- Include provenance fields: source system, refresh UTC, confidence, and key gaps.

## Authority and Assurance Gates

- Apply approval and escalation requirements from `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.
- Run protocol conformance checks from `../_shared/references/us-joint-protocol-assurance-drill.md` before high-impact recommendations.
- If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander prompts.