Agent skill · magnus919
pace-plan
Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan. Use for resilient emergency-communications paths and their ownership, triggers, check-ins, tests, and corrective actions. Do not use for generic incident status messaging, frequency or channel planning, radio programming, or unauthorized transmission and activation.
What it needs
About 4k tokens when loaded.
What this skill does
PACE Plan PACE means Primary, Alternate, Contingency, and Emergency. Use this skill to make a group's communications fallbacks operable, testable, and reviewable without inventing local facts or authority. Safety And Authority This skill can support live activation, transmission, or tests that change external state. Read-only discovery and document drafting may proceed without confirmation. Before the first real transmission, activation, live-system test, or other external mutation: Confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation. Also confirm the named activation authority permits the operational action under the applicable procedure. Plan approval by a decision-maker does not by itself authorize activation. Never infer authority from urgency, role labels, access to equipment, or possession of plan details. Destructive actions and irreversible cleanup require an explicit user directive. Do not invent frequencies, channels, talkgroups, call signs, contacts, infrastructure, regulatory permission, medical or public-safety instructions, or authority to transmit or activate. Defer to authorized operating procedures, applicable regulation, and incident leadership. Core Workflow 1. PLAN: Define the mission or essential function and every sender/receiver pair that must communicate. Inventory only authorized and available capabilities. 2. COORDINATE: Assign owners, participants, decision authority, activation authority, and handoffs. Validate that both ends can use each path. 3. OPERATE: Define contact, check-in, escalation, fallback, activation, and abandonment procedures with observable criteria. 4. TROUBLESHOOT: Check the expected tier, endpoint readiness, dependencies, and evidence before recommending a transition or handoff. 5. EXERCISE: Design an authorized, bounded test with objectives, safety limits, expected evidence, and a stop condition. Exercise paths only to the available and authorized extent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/pace-plan