Business Continuity
Create a business continuity plan for "$ARGUMENTS" with critical business function identification, RPO/RTO targets, continuity strategies, disruption scenarios, and tabletop exercise planning.
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":"security-business-continuity","workflow":"security","phase":5,"project":"<project>","event":"skipped","artifact":"05-recover.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 5 (Recover) of the NIST CSF workflow (security); 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 security 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":"security-business-continuity","workflow":"security","phase":5,"project":"<project>","event":"refused","artifact":"05-recover.md","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":"security-business-continuity","workflow":"security","phase":5,"project":"<project>","event":"started","artifact":"05-recover.md","note":""}.
Read .singularskills/security/<project>/00-govern.md. If this file does not exist, tell the user:
Phase 0 (Govern) has not been completed for "". Run a Govern skill first (e.g.,
/security-security-policy <project>), or use--skip-checksto bypass.
Process
Read context files:
- Read
references/incident-response-template.mdfor continuity workflow reference - Read
.singularskills/security/<project>/00-govern.mdfor organizational context and risk appetite
- Read
Identify critical business functions and dependencies:
- List all business functions (revenue-generating, customer-facing, internal operations, compliance)
- Rank by business impact: what is the cost per hour of downtime for each function?
- Map technology dependencies for each function (applications, databases, third-party services, infrastructure)
- Identify single points of failure in dependency chains
- Map personnel dependencies (key person risk for critical functions)
Set RPO and RTO per function:
- RPO (Recovery Point Objective) — maximum acceptable data loss per function
- RTO (Recovery Time Objective) — maximum acceptable downtime per function
- Align with business SLAs and contractual obligations
- Consider regulatory requirements for availability (financial services, healthcare)
- Document cost implications of different RPO/RTO levels to support investment decisions
Define continuity strategies:
- Active-active — multiple live instances serving traffic simultaneously (lowest RTO, highest cost)
- Active-passive — standby environment ready to activate on failure (moderate RTO, moderate cost)
- Cold standby — infrastructure provisioned on demand during disaster (highest RTO, lowest cost)
- Manual workaround — business process can continue without technology for limited period
- Select strategy per function based on RPO/RTO requirements and budget constraints
- Document decision rationale for each function
Plan for disruption scenarios:
- Data center / cloud region failure — failover to secondary region, DNS-based routing, data replication lag impact
- Cloud provider outage — multi-cloud strategy assessment, portable workload design, manual fallback
- Ransomware — air-gapped backup restoration, clean environment rebuild, negotiation policy (pay/don't pay)
- Key person unavailable — cross-training, documentation, deputy assignments, knowledge base
- Extended power/network outage — remote work activation, communication alternatives, manual processes
- For each scenario: trigger conditions, response actions, communication plan, recovery steps
Define communication plan during disruption:
- Internal communication: who is notified, how, and at what cadence
- Customer communication: status page, email, social media, support channels
- Partner/vendor communication: SLA impact notifications, joint response coordination
- Regulatory communication: if disruption affects compliance obligations
Define roles and responsibilities:
- Business Continuity Manager: owns BCP activation and coordination
- Function owners: responsible for their function's continuity procedures
- IT/Engineering: responsible for technical failover and recovery
- Communications: responsible for stakeholder updates
- Define activation authority: who can declare a business continuity event
Plan tabletop exercises:
- Conduct at minimum annually, more frequently for critical functions
- Design realistic scenarios based on threat landscape and past incidents
- Involve all key roles: business, technology, communications, legal
- Document exercise findings: what worked, what failed, what was unclear
- Update BCP based on exercise findings
- Track improvement actions from exercises to completion
Write the artifact — append to
.singularskills/security/<project>/05-recover.mdunder a## Business Continuitysection. Create the file with a# Recover — <project>heading if it does not exist; if a## Business Continuitysection already exists, replace only that section. The section contains:Business Continuity Plan
Include sections:
- Critical Functions — ranked list with dependencies and single points of failure
- RPO/RTO Targets — per function with cost justification
- Continuity Strategies — selected approach per function with rationale
- Disruption Scenarios — response plans per scenario type
- Communication Plan — stakeholder communication during disruption
- Roles and Responsibilities — BCP team structure and activation authority
- Tabletop Exercise Plan — schedule, scenarios, and improvement tracking
Output
The business continuity plan appended to .singularskills/security/<project>/05-recover.md. Present a summary to the user highlighting:
- Critical business functions and their RPO/RTO targets
- Continuity strategy selected per function
- Key disruption scenarios planned for
- Tabletop exercise schedule and approach
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"security-business-continuity","workflow":"security","phase":5,"project":"<project>","event":"finished","artifact":"05-recover.md","note":""}.
This artifact is shared by every skill of phase 5 (Recover). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Recover
workflow: security
phase: 5
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Business Continuity section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is security-business-continuity).
End your section with ### Decisions and ### Open questions (one level under your ## Business Continuity heading, so the section stays one block), 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 a penetration test or audit. This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.