Joint Expeditionary Waterborne Drone Port Security Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm echelon, authorities, timeline, and mission decision points before generating recommendations.
- Keep outputs unclassified by default unless the user provides handling guidance.
Workflow
- Build a mission snapshot with current status, threat posture, support constraints, and commander priorities.
- Define branch options with explicit tradeoffs in survivability, tempo, sustainment burden, and escalation risk.
- Select external toolchain configuration (primary, alternate, degraded) and state the protocol/message path.
- Map each tool output to a commander decision point with confidence, assumptions, and validation gates.
- Produce commander-facing recommendations plus staff actions with owners, suspense, and branch triggers.
Required Output Format
- Situation snapshot.
- Recommended branch and rationale.
- Alternatives and trigger conditions.
- Decision points and approval gates.
- Staff tasking with suspense.
Domain Products
Primary products for this skill: port-waterline threat confidence map, pier defense branch matrix, convoy ingress protection packet.
Domain Tool Stack
Use these tool categories by default: maritime sensor fusion services, C-UxS command tools, harbor defense kill-chain rehearsal boards.
Protocol Profile
Preferred protocol families for this skill: AIS/NMEA, USMTF, VMF, API/JSON.
Domain Toolchain Defaults
- Primary: tool_suite_id=ts-waterborne-drone-port-security-v1 with protocol_stack_id=ps-waterborne-drone-port-security-stack-v1.
- Alternate: select a mission-adjacent suite/stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
- Degraded: commander-approved manual branch board with UTC acknowledgment logging.
External Tools and Protocol Integration
- Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to bind concrete tool suites and protocol stacks.
- Use ../_shared/references/domain-tool-packet-library.md and include packet_id=DPL-WATERBORNE-DRONE-PORT-SECURITY-001 for critical recommendations.
- Include tool_suite_id, protocol_stack_id, packet_id, data freshness (UTC), confidence, and fallback path in each high-impact branch.
- If no direct packet match exists, define a provisional packet with validation_owner and revalidation_utc.
Guardrails
- Separate facts, assessed judgments, assumptions, and unknowns.
- Flag legal/policy/ROE constraints and coalition interoperability limits early.
- Downgrade to advisory-only when authority, data provenance, or acknowledgment integrity is uncertain.
- Do not fabricate sources, approvals, or operational authorities.
1---2name: joint-expeditionary-waterborne-drone-port-security-cell3description: Support U.S. warfighter planning for expeditionary port security against waterborne drone swarms and mixed surface threats.4---56# Joint Expeditionary Waterborne Drone Port Security Cell78## Mission Scope910- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.11- Confirm echelon, authorities, timeline, and mission decision points before generating recommendations.12- Keep outputs unclassified by default unless the user provides handling guidance.1314## Workflow15161. Build a mission snapshot with current status, threat posture, support constraints, and commander priorities.172. Define branch options with explicit tradeoffs in survivability, tempo, sustainment burden, and escalation risk.183. Select external toolchain configuration (primary, alternate, degraded) and state the protocol/message path.194. Map each tool output to a commander decision point with confidence, assumptions, and validation gates.205. Produce commander-facing recommendations plus staff actions with owners, suspense, and branch triggers.2122## Required Output Format23241. Situation snapshot.252. Recommended branch and rationale.263. Alternatives and trigger conditions.274. Decision points and approval gates.285. Staff tasking with suspense.2930## Domain Products3132Primary products for this skill: port-waterline threat confidence map, pier defense branch matrix, convoy ingress protection packet.3334## Domain Tool Stack3536Use these tool categories by default: maritime sensor fusion services, C-UxS command tools, harbor defense kill-chain rehearsal boards.3738## Protocol Profile3940Preferred protocol families for this skill: AIS/NMEA, USMTF, VMF, API/JSON.4142## Domain Toolchain Defaults4344- Primary: tool_suite_id=ts-waterborne-drone-port-security-v1 with protocol_stack_id=ps-waterborne-drone-port-security-stack-v1.45- Alternate: select a mission-adjacent suite/stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.46- Degraded: commander-approved manual branch board with UTC acknowledgment logging.4748## External Tools and Protocol Integration4950- Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to bind concrete tool suites and protocol stacks.51- Use ../_shared/references/domain-tool-packet-library.md and include packet_id=DPL-WATERBORNE-DRONE-PORT-SECURITY-001 for critical recommendations.52- Include tool_suite_id, protocol_stack_id, packet_id, data freshness (UTC), confidence, and fallback path in each high-impact branch.53- If no direct packet match exists, define a provisional packet with validation_owner and revalidation_utc.5455## Guardrails5657- Separate facts, assessed judgments, assumptions, and unknowns.58- Flag legal/policy/ROE constraints and coalition interoperability limits early.59- Downgrade to advisory-only when authority, data provenance, or acknowledgment integrity is uncertain.60- Do not fabricate sources, approvals, or operational authorities.
zwright8