什么是 业务连续性规划器？

业务连续性规划器是 Openclaw Skills 的一个专业补充，旨在保护组织的韧性。它引导用户完成识别关键业务职能、设定恢复目标以及建立明确沟通协议的复杂过程，以尽量减少技术或运营危机期间的停机时间。通过利用此技能，组织可以将抽象的灾难恢复概念转化为可操作的、数据驱动的策略，确保长期稳定。

该工具对于需要满足合规标准或保护云托管基础设施的组织特别有价值。在 Openclaw Skills 生态系统中，它弥补了技术运营与高管监督之间的鸿沟，确保在系统出现故障时，每个人都知道该给谁打电话以及该做什么。

下载入口:https://github.com/openclaw/skills/tree/main/skills/1kalin/afrexai-business-continuity

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

业务连续性规划器 应用场景

• 映射关键的创收业务职能及其复杂的技术依赖关系。
• 为 AWS 或其他云托管系统计算恢复时间目标 (RTO) 和恢复点目标 (RPO)。
• 生成正式的 BCP 和灾难恢复文档，供利益相关者签署和监管合规使用。
• 为应急响应团队建立危机沟通树和升级路径。
• 在 SaaS 或企业基础设施中引起停机前，识别并缓解单点故障。

1. 通过识别核心系统、供应商依赖关系以及每小时停机的财务影响，执行业务影响分析 (BIA)。
2. 对技术、人员、设施和供应链类别进行风险评估，以计算特定的风险评分。
3. 定义恢复策略，包括手动变通方法、主要/次要恢复方法以及每个职能的负责人。
4. 制定包含定义的升级触发因素以及内部/外部利益相关者联系人列表的沟通计划。
5. 以 Markdown 格式生成结构化的 BCP 文档，可转换为 PDF 以便立即分发。
6. 为桌面演习、模拟测试和年度 DR 故障转移测试建立测试和维护计划。

业务连续性规划器 配置指南

要在 Openclaw Skills 中激活业务连续性规划器，只需向代理提供有关您组织的基础设施和规模的基本背景信息。您可以使用如下命令启动工作流：

"为我们 40 人的 SaaS 公司创建一份业务连续性计划"
"映射我们的关键职能并为每个职能设置 RTO"

代理随后将引导您逐步完成数据收集过程，以构建您的定制计划。

业务连续性规划器 数据架构与分类体系

该技能将业务韧性数据组织成结构化的分类法，确保捕获所有元数据以进行专业报告。最终输出是一个 Markdown 文档，组织如下：

Business Continuity Planner

Build a complete Business Continuity Plan (BCP) and Disaster Recovery (DR) strategy for any organization.

What It Does

• Maps critical business functions and their dependencies
• Assigns Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO)
• Creates communication chains and escalation paths
• Generates a full BCP document ready for stakeholder sign-off
• Identifies single points of failure before they break

How to Use

Tell the agent about your business and it will walk you through building a BCP:

"Create a business continuity plan for our 40-person SaaS company"
"We need a disaster recovery plan — our main systems are AWS-hosted"
"Map our critical functions and set RTOs for each"

Process

1. Business Impact Analysis

Ask the user about:

• Core revenue-generating functions
• Customer-facing systems
• Internal operations (payroll, comms, data)
• Key vendors and third-party dependencies

For each function, determine:

• Impact of downtime (revenue loss per hour, contractual penalties, reputation damage)
• RTO — how fast must it recover? (minutes, hours, days)
• RPO — how much data loss is acceptable?

2. Risk Assessment

Identify threats across categories:

• Technology: server failure, cyberattack, data corruption, cloud outage
• People: key person risk, mass absence, skills gap
• Facilities: office access, power, connectivity
• Supply chain: vendor failure, payment disruption
• External: regulatory change, natural disaster, pandemic

Rate each: Likelihood (1-5) × Impact (1-5) = Risk Score

3. Recovery Strategies

For each critical function, define:

• Primary recovery method
• Backup/alternative approach
• Manual workaround (if systems are down)
• Responsible person + backup person
• Dependencies that must recover first

4. Communication Plan

Build a contact tree:

• Crisis management team (names, roles, phone numbers)
• Escalation triggers (what constitutes a crisis?)
• Internal notification sequence
• External stakeholder communication (clients, vendors, regulators)
• Media/PR response template

5. BCP Document Output

Generate a structured document with:

# Business Continuity Plan — [Company Name]
## Version: 1.0 | Last Updated: [Date] | Next Review: [Date + 6 months]

### 1. Purpose & Scope
### 2. Business Impact Analysis (table)
### 3. Risk Register (table with scores)
### 4. Recovery Strategies (per function)
### 5. Communication Plan & Contact Tree
### 6. IT Disaster Recovery Procedures
### 7. Testing Schedule (tabletop exercises quarterly, full test annually)
### 8. Document Control & Review Cycle

6. Testing & Maintenance

Recommend:

• Tabletop exercise quarterly — walk through a scenario verbally
• Simulation test bi-annually — actually invoke recovery procedures
• Full DR test annually — failover to backup systems
• Review trigger: after any real incident, org change, or new system deployment

Output Format

Deliver the BCP as a single markdown document the user can save, print, or convert to PDF. Include tables for the Business Impact Analysis and Risk Register.

Tips

• Start with the functions that make money. Everything else is secondary.
• A plan that exists but hasn't been tested is just a document, not a plan.
• The #1 cause of extended outages isn't technical failure — it's nobody knowing who to call.
• Keep it practical. A 5-page plan people actually read beats a 50-page plan nobody opens.