From safetysure-erp
Primary orchestrator for developing site-specific Emergency Response Plans (ERPs) aligned with AS 3745:2010 (Planning for emergencies in facilities). Guides section-by-section ERP development with template fidelity, multi-jurisdiction support (QLD, NSW, VIC, TAS, WA), variable ECO structures, shift-specific coverage models, and .docx output. Use this skill whenever developing a new ERP, building an emergency response plan, creating emergency procedures, or setting up emergency management documentation for an Australian facility. Also triggers on mentions of AS 3745 ERP development, emergency planning documents, ECO action cards, or evacuation procedures for a specific site.
npx claudepluginhub teddychenfeiyang-png/safetysure-plugins --plugin safetysure-erpThis skill uses the workspace's default tool permissions.
You are developing a site-specific Emergency Response Plan aligned with the methodology of AS 3745:2010. Work through the plan **one phase at a time**, confirming with the user before moving to the next phase. Never attempt to generate the entire ERP in a single pass — the template contains carefully crafted language that is lost when rushing.
references/ERP-Intake-Form.htmlreferences/eco-role-matrix.mdreferences/template-cover-and-toc.mdreferences/template-s01-purpose-scope.mdreferences/template-s02-key-contacts.mdreferences/template-s03-emergency-contacts.mdreferences/template-s04-facility-description.mdreferences/template-s05-epc.mdreferences/template-s06-emergency-features.mdreferences/template-s07-communications.mdreferences/template-s08-assembly-areas.mdreferences/template-s09-eco.mdreferences/template-s10-roles.mdreferences/template-s11-peeps.mdreferences/template-s12-other-considerations.mdreferences/template-s13-training.mdreferences/template-s14-management-principles.mdreferences/template-s15-eco-duties.mdreferences/template-s16-types-of-emergencies.mdreferences/template-s17-procedures.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You are developing a site-specific Emergency Response Plan aligned with the methodology of AS 3745:2010. Work through the plan one phase at a time, confirming with the user before moving to the next phase. Never attempt to generate the entire ERP in a single pass — the template contains carefully crafted language that is lost when rushing.
as-3745 reference skill — you will need it throughout for clause references.docx skill — the final output is a Word document.| Jurisdiction | Terminology | Legislation Skill | Act | Regulation |
|---|---|---|---|---|
| QLD (default) | WHS | whs-act-checker-qld + whs-regulation-checker-qld | Work Health and Safety Act 2011 (Qld) | Work Health and Safety Regulation 2011 (Qld) |
| NSW | WHS | whs-act-checker-nsw + whs-regulation-checker-nsw | Work Health and Safety Act 2011 (NSW) | Work Health and Safety Regulation 2025 (NSW) |
| VIC | OHS | ohs-act-checker-vic + ohs-regulation-checker-vic | Occupational Health and Safety Act 2004 (Vic) | Occupational Health and Safety Regulations 2017 (Vic) |
| TAS | WHS | whs-act-checker-tas + whs-regulation-checker-tas | Work Health and Safety Act 2012 (Tas) | Work Health and Safety Regulations 2022 (Tas) |
| WA | WHS | whs-act-checker-wa + whs-regulation-checker-wa | Work Health and Safety Act 2020 (WA) | Work Health and Safety (General) Regulations 2022 (WA) |
Victoria uses different terminology throughout: "employer" not "PCBU", "OHS" not "WHS", "WorkSafe Victoria" as regulator.
The ERP follows this section structure (24 template reference files in references/):
| Section | Template File | Phase |
|---|---|---|
| Cover + TOC | template-cover-and-toc.md | 6 |
| 01 — Purpose & Scope | template-s01-purpose-scope.md | 5 |
| 02 — Key Site Contacts | template-s02-key-contacts.md | 1 |
| 03 — Emergency Contacts | template-s03-emergency-contacts.md | 5 |
| 04 — Facility Description | template-s04-facility-description.md | 1 |
| 05 — EPC | template-s05-epc.md | 5 |
| 06 — Emergency Features | template-s06-emergency-features.md | 1 |
| 07 — Communications | template-s07-communications.md | 1 |
| 08 — Assembly Areas | template-s08-assembly-areas.md | 1 |
| 09 — ECO Structure | template-s09-eco.md | 2 |
| 10 — Roles & Responsibilities | template-s10-roles.md | 2 |
| 11 — PEEPs | template-s11-peeps.md | 5 |
| 12 — Other Considerations | template-s12-other-considerations.md | 5 |
| 13 — Training | template-s13-training.md | 5 |
| 14 — Emergency Management Principles | template-s14-management-principles.md | 2 (shift strategy) + 5 (boilerplate) |
| 15 — ECO Duties | template-s15-eco-duties.md | 5 |
| 16 — Types of Emergencies | template-s16-types-of-emergencies.md | 3 |
| 17 — Specific Actions (Procedures) | template-s17-procedures.md | 4 |
| 18 — Post-Incident Management | template-s18-post-incident.md | 5 |
| 19 — Fire Extinguishers | template-s19-fire-extinguishers.md | 5 |
| 20 — Fire Blankets | template-s20-fire-blankets.md | 5 |
| 21 — Fire Hose Reels | template-s21-fire-hose-reels.md | 5 |
| 22 — Appendices A–H | template-s22-appendices.md | 5 + 3 (Appendix G) |
| 23 — Glossary & References | template-s23-glossary-refs.md | 5 |
For each section, read the corresponding template file before generating content. Reproduce boilerplate text verbatim — only insert site-specific data where placeholders indicate.
Goal: Establish project parameters and gather all site data before writing any content.
ERP-Intake-Form.htmlerp-emergency-library skillreferences/ERP-Intake-Form.html)Present a summary: "Here is what I have for this project: [Client], [Site], [Jurisdiction], [Industry type], [Key details]. Shall I proceed to Phase 1?"
AS 3745 alignment: Clause 3.3 (Key Considerations)
Read these template reference files before generating content:
references/template-s02-key-contacts.mdreferences/template-s04-facility-description.mdreferences/template-s06-emergency-features.mdreferences/template-s07-communications.mdreferences/template-s08-assembly-areas.mdDraft these sections using template boilerplate with site-specific data inserted:
Present each section to the user for review. Use [INSERT: description] for any missing data.
"Phase 1 complete — site profile sections drafted. Ready for Phase 2 (ECO structure and shift management)?"
AS 3745 alignment: Clauses 5.1–5.3, Appendix F
This phase has two steps that must be completed together because the shift model directly affects the ECO structure.
Read references/eco-role-matrix.md for the full role pool and duty descriptions.
Read references/template-s09-eco.md and references/template-s10-roles.md.
Present ECO preset models as starting points, then allow full customisation:
Presets:
After selecting a preset (or starting from scratch), the user can add or remove roles. Custom roles beyond AS 3745's standard set are supported — for each custom role, capture: role title, pre-emergency duties, emergency duties, post-emergency duties, and identification colour.
The role selection drives:
If the facility operates shifts (captured in Phase 0/1), define the ECO coverage model for each shift:
| Field | Description |
|---|---|
| Shift name | Label (e.g., Day Shift, Night Shift) |
| Hours | Start and end times |
| Headcount | Typical workers on shift |
| ECO model | Which roles are staffed this shift |
| Response strategy | Full response, or evacuate-and-call |
Key principle: A night shift with 5 workers does not attempt the same response as a day shift with 50. For reduced-staffing shifts, the strategy may be "all personnel evacuate immediately to assembly area; senior person calls 000; no first-attack firefighting attempted."
Shift-specific strategy is documented in Section 14 (Emergency Management Principles). Action cards in Section 17 use a single format based on the full-staffing ECO — they do not repeat shift variations. Section 14 provides the overarching shift-specific protocol that the reader refers to.
Draft these sections:
"Phase 2 complete — ECO structure and shift management defined. Ready for Phase 3 (emergency identification and assessment)?"
AS 3745 alignment: Clause 3.2 (Emergency Identification and Analysis)
This phase is handled by the erp-emergency-assessment skill. Invoke it with the facility data gathered in Phases 0–1. If the user has already run /erp-assess independently, use those results instead of re-running.
"Phase 3 complete — [X] individual risks identified, grouped into [Y] procedure categories. Ready for Phase 4 (procedure development)?"
AS 3745 alignment: Clauses 4.1, 4.2
Read references/template-s17-procedures.md for the action card format and base procedure content.
Generate a procedure with:
Title and colour code per AS 3745 Table 4.1:
Action card table — Columns determined by the ECO roles from Phase 2. Example column structures:
Minimum ECO: Chief Warden | All Occupants Standard ECO: Chief Warden | Wardens | All Occupants | First Aid Officer Extended ECO: Chief Warden | Area/Floor Wardens | Wardens | All Occupants | First Aid Officer
Row structure per column:
Select the appropriate option for each procedure (per AS 3745 Clause 4.2.6.3):
Generate procedures one at a time, presenting each to the user for review before proceeding to the next. The template file contains base procedure text — adapt it to the facility's specific hazards, equipment, and ECO structure. Do not invent generic content where the template provides specific language.
Section 17 — All emergency response procedures with action cards.
"Phase 4 complete — [Y] emergency procedures drafted. Ready for Phase 5 (supporting sections)?"
Generate the remaining sections using template boilerplate with site-specific data. Read each template file before generating the corresponding section.
| Section | Template File | Key Customisation |
|---|---|---|
| 01 — Purpose & Scope | template-s01-purpose-scope.md | Insert jurisdiction-specific legislation from loaded legislation skills |
| 03 — Emergency Contacts | template-s03-emergency-contacts.md | Pre-populate 000, 13 11 14, 13 12 26; leave site-specific as [INSERT] |
| 05 — EPC | template-s05-epc.md | Standard AS 3745 Clause 2 content |
| 11 — PEEPs | template-s11-peeps.md | Standard AS 3745 Appendix D reference |
| 12 — Other Considerations | template-s12-other-considerations.md | Minor site-specific adaptation |
| 13 — Training | template-s13-training.md | Training table with standard entries per AS 3745 Section 6 |
| 14 — Emergency Management Principles | template-s14-management-principles.md | Complete with alert/evacuation phases + shift strategy from Phase 2 |
| 15 — ECO Duties | template-s15-eco-duties.md | Process map aligned with ECO structure from Phase 2 |
| 18 — Post-Incident Management | template-s18-post-incident.md | 10-step post-incident table |
| 19 — Fire Extinguishers | template-s19-fire-extinguishers.md | P.A.S.S. method, class selection matrix |
| 20 — Fire Blankets | template-s20-fire-blankets.md | Usage instructions |
| 21 — Fire Hose Reels | template-s21-fire-hose-reels.md | Two-person usage instructions |
| 22 — Appendices (excl. G) | template-s22-appendices.md | Register templates, checklists adapted to ECO structure |
| 23 — Glossary & References | template-s23-glossary-refs.md | Update reference list per jurisdiction |
Work through these in document order (Section 01 first, then 03, 05, etc.). For sections with mostly boilerplate, you can draft several at once and present them as a batch. For sections requiring significant customisation (01, 13, 14, 22), present individually.
"Phase 5 complete — all supporting sections drafted. Ready for Phase 6 (assembly and review)?"
Read references/template-cover-and-toc.md for the cover page and table of contents format.
Compile all sections into a single Word document (.docx) using the docx skill. The document order is:
Review the assembled document against this checklist:
[INSERT] placeholders flagged for user attentionPresent the completeness summary. List any [INSERT] placeholders that still need user input. Save the document to the working folder.
"Your Emergency Response Plan has been saved as [filename].docx. There are [N] placeholder fields that still need site-specific information — I have listed these above. The document is ready for transfer to InDesign for final formatting."
These apply throughout all phases:
[INSERT: description of required information] for any data not yet provided[INSERT] placeholders and flag themerp-emergency-assessment skill is not available, guide the user through a simplified manual hazard identification using the erp-emergency-library scenarios as prompts