Resilience Improvement
Identify and implement resilience improvements for "$ARGUMENTS" by aggregating findings from incidents, DR tests, and penetration tests, prioritizing by risk reduction, and tracking implementation progress.
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-resilience-improvement","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-resilience-improvement","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-resilience-improvement","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
.singularskills/security/<project>/00-govern.mdfor organizational context and risk appetite - Read
.singularskills/security/<project>/04-respond.mdif it exists, for incident response findings - Read
.singularskills/security/<project>/05-recover.mdif it exists, for recovery test findings
- Read
Aggregate findings from all sources:
- Incidents — corrective actions from post-incident reviews, root causes, contributing factors
- DR tests — failures and gaps discovered during disaster recovery exercises
- Penetration tests — vulnerabilities found, exploitation paths, remediation recommendations
- Tabletop exercises — process gaps, communication failures, unclear responsibilities
- Audit findings — compliance gaps, control deficiencies, auditor recommendations
- Normalize findings into a common format: finding ID, source, description, severity, affected area
Identify patterns and systemic weaknesses:
- Group findings by category (access control, monitoring, configuration, process, training)
- Identify recurring themes across multiple sources (same weakness found by incident AND pen test)
- Detect trends over time (are certain categories improving or degrading?)
- Identify systemic issues vs. one-off problems
- Map weaknesses to NIST CSF functions (Identify, Protect, Detect, Respond, Recover)
Prioritize improvements by risk reduction and effort:
- Risk reduction — how much does this improvement reduce overall risk? (high/medium/low)
- Effort — how much time and resources are required? (high/medium/low)
- Quick wins — high risk reduction, low effort (prioritize first)
- Strategic investments — high risk reduction, high effort (plan and budget)
- Nice-to-haves — low risk reduction, low effort (batch with other work)
- Defer — low risk reduction, high effort (reconsider later)
- Use risk matrix to visualize prioritization
Create improvement roadmap:
- Immediate (0–30 days) — quick wins and critical fixes
- Short-term (1–3 months) — significant improvements requiring moderate effort
- Medium-term (3–6 months) — strategic investments and architectural changes
- Long-term (6–12 months) — systemic improvements and cultural changes
- Assign each improvement: owner, deadline, resources needed, success criteria, dependencies
Track implementation:
- Define tracking mechanism (project management tool, security dashboard, regular review meetings)
- Set review cadence (monthly for active items, quarterly for roadmap review)
- Escalate blocked or overdue items
- Report progress to security leadership and stakeholders
Measure improvement:
- MTTR (Mean Time to Recover) — track trend over time (should decrease)
- Incident frequency — track by category (should decrease for addressed categories)
- Recovery success rate — percentage of DR tests that meet RTO/RPO (should increase)
- Vulnerability remediation time — time from discovery to fix (should decrease)
- Pen test findings — number and severity trend over successive tests (should decrease)
- Define baseline measurements and improvement targets
Integrate findings into security strategy:
- Update risk register with new risks identified
- Update security policies and standards based on lessons learned
- Feed improvements back into security training program
- Update threat model with newly discovered attack vectors
- Inform budget planning with quantified risk reduction data
Write the artifact — append to
.singularskills/security/<project>/05-recover.mdunder a## Resilience Improvementsection. Create the file with a# Recover — <project>heading if it does not exist; if a## Resilience Improvementsection already exists, replace only that section. The section contains:- Findings Aggregation — normalized findings from all sources
- Pattern Analysis — recurring themes, trends, and systemic weaknesses
- Prioritization Matrix — risk reduction vs. effort for each improvement
- Improvement Roadmap — phased plan with owners and deadlines
- Metrics and Tracking — KPIs, baselines, and targets
- Strategy Integration — how findings feed back into security program
Output
The resilience improvement plan appended to .singularskills/security/<project>/05-recover.md. Present a summary to the user highlighting:
- Key patterns and systemic weaknesses identified
- Quick wins prioritized for immediate action
- Improvement roadmap with timeline and owners
- Metrics defined for measuring progress
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-resilience-improvement","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 ## Resilience Improvement section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is security-resilience-improvement).
End your section with ### Decisions and ### Open questions (one level under your ## Resilience Improvement 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.