Operate and improve Primary, Alternate, Contingency, and Emergency communications plans.
npx skills add https://github.com/magnus919/agent-skills --skill pace-plan-magnus919
Please help me install this Agent Skill. Skill: pace-plan Source: https://github.com/magnus919/agent-skills/tree/main/pace-plan Command: npx skills add https://github.com/magnus919/agent-skills --skill pace-plan-magnus919
This Skill solves the common failure of emergency communications plans that are written but never operated, by turning static tables into an active, owner-approved operating cycle that prevents unsafe improvisation.
Use the pace-plan skill to audit our current emergency communications worksheet and identify any missing activation triggers or shared infrastructure dependencies.
High-intent search queries and answers about installing and using this skill.
A PACE plan systematically defines Primary, Alternate, Contingency, and Emergency communications paths while establishing clear activation authorities, transition triggers, and handoff procedures to ensure teams know exactly when and how to switch communication methods.
Auditing emergency communications plans involves systematically defining your Primary, Alternate, Contingency, and Emergency paths to identify shared infrastructure dependencies, like a vulnerable power source, that could cause simultaneous failure across multiple communication systems.
Establish activation authorities and transition triggers by applying operational governance to your communications plan, defining clear handoff procedures and check-in protocols that prevent unsafe improvisation and ensure authorized path management during disasters.
Yes, you can use this for technology-neutral emergency communications planning because it satisfies requirements for authority-safe planning without inventing local facts or unauthorized transmission procedures, keeping your technology and platform choices completely independent.
Static emergency communications plans fail during a disaster because they are written but never operated, leading to unsafe improvisation. Converting static tables into an active, owner-approved operating cycle with regular tests and corrective actions prevents this failure.
Yes, this approach supports regular testing and corrective actions by managing the full operating cycle, which includes exercising and improving your authorized communications paths to build resilience through continuous check-ins and troubleshooting.
simon-downesAudit implementation plans for completeness, unresolved decisions, and implementability.
UBR-JMAIdentify early friction signals and establish behavioral agreements for community conflict prevention.
nikhilvallishayeeActivate joy protocols to reframe navigation as playful exploration.
guia-matthieuCoordinate crisis response using structured playbooks and communication templates.
