Support U.S. warfighter planning and decision support for Expeditionary Laser Dazzle Aircrew Incident Response Cell. Use when missions require aircrew laser-dazzle incident triage, sortie-risk adjustment, and base defense evidence synchronization, integrated options, and protocol-aware staff outputs.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Support U.S. warfighter planning and decision support for Expeditionary Laser Dazzle Aircrew Incident Response Cell. Use when missions require aircrew laser-dazzle incident triage, sortie-risk adjustment, and base defense evidence synchronization, integrated options, and protocol-aware staff outputs.
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
Frame the mission problem using current intent, threat indicators, operational constraints, and known assumptions.
Define measurable objectives, risk thresholds, branch conditions, and indicators that would invalidate the preferred plan.
Build a recommended option and at least two alternatives with explicit tradeoffs in tempo, survivability, sustainment load, and escalation risk.
Integrate dependencies across joint functions: command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information.
Convert the decision into execution-ready products with owners, suspense dates, coordination links, and required reports.
Required Output Format
Deliver results in this order:
Situation snapshot: current conditions and key changes since the last update.
Recommended option: one clearly stated recommendation and rationale.
Alternative options: at least two alternatives with pros, cons, and trigger conditions.
Decision points: what must be decided now, later, or pre-delegated.
Staff tasking: who does what by when.
Domain Products
Primary products for this skill: aircrew incident triage board, sortie adaptation matrix, evidence handoff packet.
Domain Tool Stack
Use these tool categories as the default stack for this skill: aviation safety event correlators, electro-optical exposure risk estimators, legal evidence custody ledgers.
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, USMTF, NIEM, API/JSON.
Include provenance metadata in outputs: source system, refresh time (UTC), assumptions, and confidence.
Interoperability Validation Checklist
Run the mission assurance workflow 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.
Tool Protocol Playbooks
Use protocol examples in ../_shared/references/tool-protocol-playbooks.md to produce operator-ready tool invocation packets.
Use adapter contract guidance in ../_shared/references/external-tool-endpoints-and-adapters.md to define endpoint schemas, transport, and fallback behavior.
Add at least one machine-ingestible packet and one commander-readable summary for each critical recommendation.
Domain Tool Packet Library
Use scenario packets in ../_shared/references/domain-tool-packet-library.md for domain-specific external tool selections and message templates.
Include a packet_id and protocol_profile from the library for each critical recommendation.
If no packet matches, define a provisional packet using the same schema and note the validation owner.
Domain Data Contract
Use mapping guidance in ../_shared/references/joint-mission-data-contracts.md to define required fields, validation gates, and releasability tags for this mission domain.
Ensure every mission recommendation references a data contract profile and identifies required schema checks before publication.
Operational Learning Loop
Use ../_shared/references/operational-learning-and-after-action-loop.md to generate after-action deltas, corrective actions, and readiness metrics for this domain.
Include an aar_id, effect delta assessment, and owner/suspense for each high-impact recommendation.
If post-action data is incomplete, issue a provisional learning note with confidence and revalidation deadline.
Readiness Certification Evidence Pack
Use ../_shared/references/readiness-certification-evidence-pack.md to define mission-essential task evidence, evaluator triggers, and certification confidence scoring.
Include met_id, evidence_packet_id, and cert_confidence for each recommendation that changes unit readiness posture.
If required evidence is missing, mark status as provisional and assign closure actions with suspense.
Protocol Execution Sequence
Execute the Core Integration Protocol from ../_shared/references/external-tools-protocols.md as an explicit step sequence, not as guidance only.
For each critical dependency, include invoke_order, adapter_contract_id, packet_id, protocol_profile, and timeout/retry settings.
Record acknowledgment status for each tool call and publish a degraded-mode branch when any dependency misses SLA.
Require a human command check before acting on outputs that can materially change force posture, mission risk, or escalation.
Domain Toolchain Profile Binding
Use ../_shared/references/domain-toolchain-profiles.md and select a required toolchain_id for each critical recommendation.
Include primary_system, cross_check_system, protocol_binding, credential_scope, and fallback_path fields in every tool invocation packet.
Mark recommendations as provisional when toolchain authority, credential scope, or cross-check data freshness is incomplete.
Tool Health and Trust Monitoring
Use ../_shared/references/tool-health-and-trust-monitoring.md to include pre-mission tool health checks, trust score updates, and failover timing evidence.
Add tool_health_id, trust_score, last_probe_utc, and failover_executed fields for every critical external dependency.
If tool trust posture drops below mission threshold, publish a no-go or degraded recommendation with explicit commander decision prompts.
U.S. Joint Protocol Assurance Drill
Use ../_shared/references/us-joint-protocol-assurance-drill.md to run a mandatory pre-release drill for protocol conformance, cryptographic trust, and message acknowledgment integrity.
Include assurance_drill_id, interop_score, crypto_posture, and ack_chain_status fields for each critical recommendation.
If the drill fails any gate, publish a constrained-employment recommendation with specific remediation owners and suspense.
Joint Operations External Toolchain Profiles
Use ../_shared/references/joint-operations-external-toolchain-profiles.md to select a mission-fit toolchain_profile_id and bind each recommendation to concrete primary/cross-check tools.
Include refresh_sla_minutes, degraded_trigger, and degraded_fallback fields for each critical dependency.
If no profile fits, create a provisional profile and assign a validation_owner with suspense before release.
Human-Agent Command Escalation Matrix
Use ../_shared/references/human-agent-command-escalation-matrix.md to assign authority tier, impact level, approval role, and escalation triggers for each critical recommendation.
Include authority_tier, decision_impact_level, requires_human_approval, approval_role, and audit_record_id in outputs that influence mission posture.
If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander decision prompts.
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 Defaults
Primary: tool_suite_id=ts-expeditionary-laser-dazzle-aircrew-incident-response-cell-v1 with protocol_stack_id=ps-expeditionary-laser-dazzle-aircrew-incident-response-cell-stack-v1.
Alternate: tool_suite_id=ts-air-missile-defense-early-warning-network-resilience-cell-v1 with protocol_stack_id=ps-air-missile-defense-early-warning-network-resilience-cell-stack-v1.
Degraded: use authenticated voice/readback + UTC acknowledgment ledger + manual fallback board.
