| name | expeditionary-hypersonic-strike-battle-damage-and-restrike-cell |
| description | Support U.S. warfighter planning and decision support for hypersonic strike battle damage assessment and rapid restrike sequencing. Use when missions require compressed kill-chain verification, residual target viability assessment, and protocol-aware restrike recommendations. |
Expeditionary Hypersonic Strike Battle Damage and Restrike Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain.
- Confirm echelon, operating environment, authority limits, timeline, and command decision points before analysis.
- Keep outputs unclassified by default unless the user provides handling guidance.
Workflow
- Frame the mission with these core inputs: strike package telemetry, sensor-to-target timelines, post-strike ISR quality, collateral constraints.
- Define assumptions, confidence bounds, and invalidation triggers.
- Build a primary and at least two alternate options with tradeoffs in tempo, survivability, sustainment, and escalation risk.
- Bind each option to concrete external tools, transport/message protocols, and degraded-mode fallbacks.
- Produce commander-facing recommendations and staff tasking with owners and suspense dates.
Required Output Format
- Situation snapshot and key changes.
- Recommended option and rationale.
- Alternatives with trigger conditions.
- Decision points (now, later, pre-delegate).
- Staff tasking and suspense dates.
Domain Products
Primary products: hypersonic BDA confidence board, restrike decision packet, battle-damage uncertainty and branch matrix.
External Tool and Protocol Requirements
- Prioritize tool families: multi-INT BDA fusion suites, target-system vulnerability graph tools, dynamic targeting decision aids.
- Prioritize protocol/message bindings: VMF, Link 16 J-series, USMTF.
- Select one profile from ../_shared/references/joint-operations-external-toolchain-profiles.md.
- Select one packet from ../_shared/references/domain-tool-packet-library.md.
- Bind each recommendation to a concrete suite/stack entry in ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
Required Metadata Fields
Include these fields in every critical recommendation:
- tool_suite_id
- protocol_stack_id
- toolchain_profile_id
- packet_id
- protocol_profile
- primary_system
- cross_check_system
- refresh_sla_minutes
- degraded_trigger
- degraded_fallback
- authority_tier
- approval_role
- trust_score
- validation_owner
Guardrails
- Separate observed facts, assessed judgments, and unknowns.
- Flag legal, policy, ROE, and coalition interoperability constraints early.
- Require explicit human command review before any recommendation that could materially change force posture or escalation risk.
- Do not fabricate authorities, classified sources, or approvals.
