agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/business-continuity-planner/SKILL.md

business-continuity-planner

Skill1 starsChanged 25 days agoMITView on GitHub

Designs continuity and recovery plans when critical services must withstand technology disruption and supplier failure.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before resilience testing, after major system change, or when recovery expectations and dependencies are unclear.

    line 9
  2. Distinctive:

    Create scenario exercises, evidence capture and plan-maintenance cadence.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Business Continuity Planner

When to use it

Use before resilience testing, after major system change, or when recovery expectations and dependencies are unclear.

What Claude needs

  • client-context.md for business background
  • Critical services, process owners and service expectations
  • Systems, people, facilities, data and supplier dependencies
  • Existing recovery plans, incidents and test results

Method

  1. Conduct a business impact analysis for priority services and disruption durations.
  2. Define maximum tolerable disruption, recovery time and data recovery objectives.
  3. Map minimum resource needs and single points of failure for each service.
  4. Design continuity options for loss of systems, data, people, premises and suppliers.
  5. Assign activation criteria, decision rights, communications and restoration steps.
  6. Create scenario exercises, evidence capture and plan-maintenance cadence.

Output format

Deliver a service recovery table, dependency map, activation playbook and exercise schedule. Include roles, triggers, workarounds and restoration criteria.

Quality checks

  • Recovery targets reflect business impact and technical capability.
  • Workarounds are feasible with available people and information.
  • Plans specify activation authority, dependencies and test evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.