# Joint Expeditionary Portable Atc Tower Tacan And Runway Services Reconstitution Cell

> Support U.S. warfighter planning for expeditionary portable ATC tower, TACAN, and runway services reconstitution when austere or battle-damaged airfields must resume flight operations fast.

- Skill: `zwright8/joint-expeditionary-portable-atc-tower-tacan-and-runway-serv` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/joint-expeditionary-portable-atc-tower-tacan-and-runway-serv`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/joint-expeditionary-portable-atc-tower-tacan-and-runway-serv/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-expeditionary-portable-atc-tower-tacan-and-runway-serv

---


# Joint Expeditionary Portable ATC Tower TACAN And Runway Services Reconstitution 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 using these core inputs: sortie demand, runway status, ATC/TACAN equipment state, weather, and airspace constraints.
2. Identify assumptions, decision thresholds, and what reporting or indicators would invalidate the current reconstitution plan.
3. Build primary and alternate options with explicit tradeoffs in sortie tempo, safety margin, sustainment burden, and exposure 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 this skill: airfield services restoration ladder, portable ATC and TACAN emplacement plan, sortie release constraints matrix.

## Domain Tool Stack

Use these tool categories as the default stack for this skill: portable tower readiness board, TACAN calibration queue, runway services status tracker, austere airfield airspace overlay.

## External Tools and Protocol Integration

- Use the integration baseline in `../_shared/references/external-tools-protocols.md` and select specific systems-of-record aligned to this mission.
- Use protocol examples in `../_shared/references/tool-protocol-playbooks.md` to produce operator-ready tool invocation packets.
- Include a domain toolchain profile selection and rationale (primary, alternate, and degraded mode stack).
- Use at least one primary source and one cross-check source before final recommendations.
- Prefer these protocol families for this skill: AIXM/FIXM, VMF, USMTF, API/JSON, signed airfield equipment manifests.
- Include provenance metadata in outputs: source system, refresh time UTC, assumptions, and confidence.

## Interoperability Validation Checklist

- Run mission assurance checks in `../_shared/references/mission-assurance-checklist.md` before final release.
- Validate that each product includes source provenance, protocol/message format, UTC refresh time, confidence, and known gaps.
- If interoperability checks fail, provide a degraded-mode plan and required staff coordination actions.

## Tool Invocation Contract

- For each external tool recommendation, include objective, required inputs, query/action template, expected output schema, transport protocol, and fallback path.
- Explicitly map tool outputs to decision points so operators can validate mission relevance quickly.
- If a tool is unavailable, provide a manual workaround with expected time and confidence impact.

## Guardrails

- Flag gaps where assumptions exceed evidence.
- Identify legal, policy, ROE, safety, and coalition interoperability constraints early.
- Separate facts, assessed judgments, and unknowns.
- Do not fabricate classified sources, authorities, or approvals.

## Mission Tool Authority Gates

- Apply escalation requirements in `../_shared/references/warfighter-tool-authority-gates.md` for high-consequence recommendations.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for recommendations that can alter mission posture.
- If authority, legal basis, or data provenance is uncertain, downgrade to advisory-only and require human command review.

## Cross-Domain Integration Playbook

- Use `../_shared/references/cross-domain-integration-playbook.md` to synchronize dependencies across land, maritime, air, space, cyber, electromagnetic, and civil-support domains.
- Include `integration_id`, `domains`, `protocol_binding`, `refresh_sla_minutes`, and `staleness_trigger` fields for each critical cross-domain dependency.
- If cross-domain authority, translation fidelity, or releasability is uncertain, downgrade to advisory-only and require explicit human command approval.

## Mission Tool and Protocol Catalog Binding

- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` to select concrete tool suites and protocol stacks for this domain.
- Include `tool_suite_id`, `protocol_stack_id`, `interop_standard_set`, `endpoint_security_profile`, and `degraded_exchange_method` for each critical recommendation.
- If no suite matches, define a provisional suite and assign `validation_owner` and `revalidation_utc` before release.

## Domain Toolchain Override (2026-03-14, Expansion Wave L Addendum)

- Primary: `tool_suite_id=ts-joint-expeditionary-portable-atc-tower-tacan-runway-services-v1` with `protocol_stack_id=ps-joint-expeditionary-portable-atc-tower-tacan-runway-services-stack-v1`.
- Alternate: `tool_suite_id=ts-airfield-recovery-v1` with `protocol_stack_id=ps-cop-event-sharing-stack-v1`.
- Add `packet_id=DPL-PORTABLE-ATC-TACAN-001` for branches that materially alter sortie release timing, airfield serviceability, or risk acceptance.