ISO 22301 Assessment
Assess ISO 22301 Business Continuity Management System (BCMS) compliance for "$ARGUMENTS". Evaluate business impact analysis, continuity strategies, plans, exercise program, and documentation requirements.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run /compliance-regulatory-landscape <project> first, or use --skip-checks to bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.md for GRC methodology reference
- Read
references/assessment-template.md for output structure
- Read
.singularskills/compliance/<project>/00-scope.md for scope and control framework context
BCMS context and scope (Clauses 4-5):
- Assess organizational context for business continuity (internal/external issues, interested parties)
- Evaluate BCMS scope definition (organizational units, locations, products/services)
- Review leadership commitment and BC policy
- Assess roles, responsibilities, and authorities for business continuity
- Evaluate resource allocation and competency requirements
Business Impact Analysis (BIA):
- Assess BIA methodology and completeness
- Evaluate identification of prioritized activities and their dependencies
- Review Maximum Tolerable Period of Disruption (MTPD) for each prioritized activity
- Assess Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO)
- Evaluate Minimum Business Continuity Objectives (MBCO)
- Review resource requirements for recovery (people, facilities, technology, information, suppliers)
- Assess BIA review and update cadence
Risk assessment for disruption scenarios:
- Assess risk assessment methodology aligned with BIA findings
- Evaluate threat identification across categories (natural, technological, human-caused, pandemic, supply chain)
- Review likelihood and impact scoring for disruption scenarios
- Assess risk treatment decisions (accept, mitigate, transfer, avoid)
- Evaluate alignment between risk assessment outcomes and continuity strategies
Business continuity strategies:
- Prevention and mitigation: Assess proactive measures to reduce disruption likelihood and impact
- Response strategies: Evaluate immediate response procedures for prioritized activities
- Recovery strategies: Assess strategies for restoring prioritized activities within RTO
- Evaluate strategy options analysis (cost vs. risk reduction)
- Review resource requirements for each strategy (alternate sites, technology, staffing)
- Assess supply chain and third-party continuity considerations
Business continuity plans:
- Incident response procedures: Assess initial response, escalation, and communication procedures
- Crisis management: Evaluate crisis management team structure, decision-making, and stakeholder communication
- Recovery procedures: Assess step-by-step recovery plans for prioritized activities
- Review plan activation criteria and authority
- Evaluate plan accessibility (offline access, distributed copies, mobile access)
- Assess plan maintenance and version control procedures
Exercise program:
- Assess exercise program scope and frequency
- Evaluate exercise types: desktop/tabletop exercises, simulation exercises, full-scale exercises
- Review exercise scenarios and coverage of disruption types
- Assess post-exercise evaluation and lessons learned documentation
- Evaluate corrective action tracking from exercise findings
- Review exercise participation across organizational levels
Performance evaluation and improvement (Clauses 9-10):
- Assess monitoring, measurement, analysis, and evaluation of BCMS effectiveness
- Evaluate internal audit program for business continuity
- Review management review process and outcomes
- Assess continual improvement mechanisms and corrective action procedures
Documentation assessment:
- Evaluate BC policy documentation
- Assess BIA results documentation and currency
- Review risk assessment documentation
- Evaluate recovery strategies documentation
- Assess BC plans documentation and accessibility
- Review exercise records and post-exercise reports
- Evaluate change management documentation for BCMS updates
Write the artifact to .singularskills/compliance/<project>/01-assess/iso22301.md following the assessment template structure with:
- BCMS Framework — context, scope, policy, and governance
- Business Impact Analysis — methodology, MTPD/RTO/RPO coverage, and completeness
- Risk Assessment — disruption scenarios, scoring, and treatment decisions
- Continuity Strategies — prevention, response, and recovery approach
- BC Plans — incident response, crisis management, and recovery procedures
- Exercise Program — types, frequency, coverage, and lessons learned
- Performance Evaluation — audit, review, and improvement mechanisms
- Documentation — completeness and currency assessment
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The ISO 22301 assessment written to .singularskills/compliance/<project>/01-assess/iso22301.md. Present a summary to the user highlighting:
- Overall BCMS maturity and certification readiness
- BIA completeness and RTO/RPO coverage across prioritized activities
- Exercise program effectiveness and coverage
- Top 3 gaps requiring remediation
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-iso22301
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.
1---2name: compliance-iso223013description: Assess ISO 22301 business continuity management system readiness — BIA with RTO and RPO, disruption risk assessment, continuity strategies and plans, and the exercise program. Use when the user wants ISO 22301 certification or must prove a certifiable continuity program and wants to assess its own BCMS. Not for writing the continuity plan itself; see /security-business-continuity.4metadata:5 source: https://skillmd.com/skills/bromso/compliance-iso223016 argument-hint: "[project] [--skip-checks]"7 workflow: compliance8 phase: 19 artifact: 01-assess/10---1112# ISO 22301 Assessment1314Assess ISO 22301 Business Continuity Management System (BCMS) compliance for "$ARGUMENTS". Evaluate business impact analysis, continuity strategies, plans, exercise program, and documentation requirements.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 1 (Assess) of the GRC Lifecycle workflow (`compliance`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `compliance` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}`.2324Read `.singularskills/compliance/<project>/00-scope.md`. If this file does not exist, tell the user:2526> Phase 0 (Scope) has not been completed for "<project>". Run `/compliance-regulatory-landscape <project>` first, or use `--skip-checks` to bypass.2728## Process29301. **Read context files:**31 - Read `references/grc-lifecycle-guide.md` for GRC methodology reference32 - Read `references/assessment-template.md` for output structure33 - Read `.singularskills/compliance/<project>/00-scope.md` for scope and control framework context34352. **BCMS context and scope (Clauses 4-5):**36 - Assess organizational context for business continuity (internal/external issues, interested parties)37 - Evaluate BCMS scope definition (organizational units, locations, products/services)38 - Review leadership commitment and BC policy39 - Assess roles, responsibilities, and authorities for business continuity40 - Evaluate resource allocation and competency requirements41423. **Business Impact Analysis (BIA):**43 - Assess BIA methodology and completeness44 - Evaluate identification of prioritized activities and their dependencies45 - Review Maximum Tolerable Period of Disruption (MTPD) for each prioritized activity46 - Assess Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO)47 - Evaluate Minimum Business Continuity Objectives (MBCO)48 - Review resource requirements for recovery (people, facilities, technology, information, suppliers)49 - Assess BIA review and update cadence50514. **Risk assessment for disruption scenarios:**52 - Assess risk assessment methodology aligned with BIA findings53 - Evaluate threat identification across categories (natural, technological, human-caused, pandemic, supply chain)54 - Review likelihood and impact scoring for disruption scenarios55 - Assess risk treatment decisions (accept, mitigate, transfer, avoid)56 - Evaluate alignment between risk assessment outcomes and continuity strategies57585. **Business continuity strategies:**59 - **Prevention and mitigation:** Assess proactive measures to reduce disruption likelihood and impact60 - **Response strategies:** Evaluate immediate response procedures for prioritized activities61 - **Recovery strategies:** Assess strategies for restoring prioritized activities within RTO62 - Evaluate strategy options analysis (cost vs. risk reduction)63 - Review resource requirements for each strategy (alternate sites, technology, staffing)64 - Assess supply chain and third-party continuity considerations65666. **Business continuity plans:**67 - **Incident response procedures:** Assess initial response, escalation, and communication procedures68 - **Crisis management:** Evaluate crisis management team structure, decision-making, and stakeholder communication69 - **Recovery procedures:** Assess step-by-step recovery plans for prioritized activities70 - Review plan activation criteria and authority71 - Evaluate plan accessibility (offline access, distributed copies, mobile access)72 - Assess plan maintenance and version control procedures73747. **Exercise program:**75 - Assess exercise program scope and frequency76 - Evaluate exercise types: desktop/tabletop exercises, simulation exercises, full-scale exercises77 - Review exercise scenarios and coverage of disruption types78 - Assess post-exercise evaluation and lessons learned documentation79 - Evaluate corrective action tracking from exercise findings80 - Review exercise participation across organizational levels81828. **Performance evaluation and improvement (Clauses 9-10):**83 - Assess monitoring, measurement, analysis, and evaluation of BCMS effectiveness84 - Evaluate internal audit program for business continuity85 - Review management review process and outcomes86 - Assess continual improvement mechanisms and corrective action procedures87889. **Documentation assessment:**89 - Evaluate BC policy documentation90 - Assess BIA results documentation and currency91 - Review risk assessment documentation92 - Evaluate recovery strategies documentation93 - Assess BC plans documentation and accessibility94 - Review exercise records and post-exercise reports95 - Evaluate change management documentation for BCMS updates969710. **Write the artifact** to `.singularskills/compliance/<project>/01-assess/iso22301.md` following the assessment template structure with:98 - **BCMS Framework** — context, scope, policy, and governance99 - **Business Impact Analysis** — methodology, MTPD/RTO/RPO coverage, and completeness100 - **Risk Assessment** — disruption scenarios, scoring, and treatment decisions101 - **Continuity Strategies** — prevention, response, and recovery approach102 - **BC Plans** — incident response, crisis management, and recovery procedures103 - **Exercise Program** — types, frequency, coverage, and lessons learned104 - **Performance Evaluation** — audit, review, and improvement mechanisms105 - **Documentation** — completeness and currency assessment106 - **Evidence Inventory** — existing evidence and evidence gaps107 - **Remediation Priorities** — ranked list of gaps to address108109## Output110111The ISO 22301 assessment written to `.singularskills/compliance/<project>/01-assess/iso22301.md`. Present a summary to the user highlighting:112- Overall BCMS maturity and certification readiness113- BIA completeness and RTO/RPO coverage across prioritized activities114- Exercise program effectiveness and coverage115- Top 3 gaps requiring remediation116117**Record the run.** After you have written the artifact, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"compliance-iso22301","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}`.118119Open the artifact with this frontmatter (`agent` is the agent you run in, or `unknown`; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`):120121```yaml122---123skill: compliance-iso22301124workflow: compliance125phase: 1126project: <project>127started: <ISO timestamp>128finished: <ISO timestamp>129agent: <the agent you run in, or "unknown">130gate: <passed|skipped>131---132```133134End the artifact with `## Decisions` and `## Open questions`, in this shape:135136```markdown137## Decisions138- <what was chosen> — <why> — <what was rejected>139140## Open questions141- <what the next phase or a reviewer must settle>142```143144End the artifact with this paragraph, verbatim:145146> **Not legal or audit advice.** This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.