Gap Analysis
Aggregate findings across all assessments for "$ARGUMENTS" into a prioritized gap register. Deduplicate gaps that appear across multiple regulations and score by risk, effort, and regulatory urgency.
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-gap-analysis","workflow":"compliance","phase":2,"project":"<project>","event":"skipped","artifact":"02-remediate.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 2 (Remediate) 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-gap-analysis","workflow":"compliance","phase":2,"project":"<project>","event":"refused","artifact":"02-remediate.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":"compliance-gap-analysis","workflow":"compliance","phase":2,"project":"<project>","event":"started","artifact":"02-remediate.md","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-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and control framework context - Read all assessment files from
.singularskills/compliance/<project>/01-assess/directory
- Read
Aggregate findings:
- Extract all non-compliant and partially-compliant findings from each assessment
- Normalize finding descriptions for consistent comparison
- Identify common root causes across findings
Deduplicate gaps:
- Identify the same gap appearing across multiple regulation assessments
- Merge duplicates into a single gap entry listing all affected regulations
- Preserve regulation-specific nuances in the merged entry
Score each gap:
- Risk score (1-10): What happens if not addressed? Consider regulatory penalties, data breach exposure, business disruption, reputational damage
- Effort score (1-10): Implementation complexity — technical difficulty, organizational change required, third-party dependencies, timeline
- Regulatory urgency (1-10): Deadline proximity, active enforcement, customer-blocking potential
Prioritize and categorize:
- Calculate weighted priority score (risk 40%, urgency 35%, inverse effort 25%)
- Identify quick wins — low effort, high risk reduction
- Identify critical gaps — high risk regardless of effort
- Identify strategic improvements — high effort but significant long-term value
Write the artifact — append to
.singularskills/compliance/<project>/02-remediate.mdunder a## Gap Analysissection. Create the file with a# Remediate — <project>heading if it does not exist; if a## Gap Analysissection already exists, replace only that section. The section contains:- Gap Register — table with gap ID, description, affected regulations, risk score, effort score, urgency score, weighted priority
- Quick Wins — gaps that can be closed rapidly with high impact
- Critical Gaps — highest risk items requiring immediate attention
- Root Cause Analysis — common themes across gaps
- Cross-Regulation Impact — gaps that affect the most regulations
Output
The gap analysis appended to .singularskills/compliance/<project>/02-remediate.md. Present a summary to the user highlighting:
- Total number of unique gaps identified
- Number of quick wins
- Top 5 highest-priority gaps
- Cross-regulation coverage opportunities
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":"compliance-gap-analysis","workflow":"compliance","phase":2,"project":"<project>","event":"finished","artifact":"02-remediate.md","note":""}.
This artifact is shared by every skill of phase 2 (Remediate). 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: Remediate
workflow: compliance
phase: 2
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Gap Analysis section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is compliance-gap-analysis).
End your section with ### Decisions and ### Open questions (one level under your ## Gap Analysis 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 legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.