Compliance Reporting
Generate compliance status reports for "$ARGUMENTS" at three levels — executive summary, detailed operational, and customer-facing — to communicate compliance posture to all stakeholders.
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-compliance-reporting","workflow":"compliance","phase":4,"project":"<project>","event":"skipped","artifact":"04-monitor.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 4 (Monitor) 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-compliance-reporting","workflow":"compliance","phase":4,"project":"<project>","event":"refused","artifact":"04-monitor.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-compliance-reporting","workflow":"compliance","phase":4,"project":"<project>","event":"started","artifact":"04-monitor.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 applicable regulations - Read
.singularskills/compliance/<project>/01-assess/*.mdfor per-regulation assessment results and scores - Read
.singularskills/compliance/<project>/02-remediate.mdfor gap and remediation status - Read
.singularskills/compliance/<project>/03-certify.mdfor certification status - Read
.singularskills/compliance/<project>/04-monitor.mdfor monitoring and calendar data
- Read
Executive summary report:
- Overall compliance score (weighted across all regulations)
- RAG (Red/Amber/Green) status per regulation
- Key risks requiring leadership attention
- Resource asks — budget, headcount, tools
- Progress since last report (trend data)
- Upcoming milestones and deadlines
Detailed operational report:
- Per-regulation status with control-level detail
- Open findings with aging and remediation status
- Evidence collection status and gaps
- Audit preparation progress
- Team workload and capacity
- Detailed risk register with mitigations
Customer-facing report:
- Trust page content — certifications held, security overview
- SOC 2 report summary (bridge letter if report is pending)
- Compliance certifications held with validity dates
- Security and privacy commitments
- Sub-processor list and data processing transparency
- FAQ for common customer security questions
Reporting cadence:
- Monthly: operational report to security/compliance team
- Quarterly: executive summary to leadership/board
- Annually: strategic compliance review
- On-demand: customer-facing reports for sales enablement
- Define report distribution lists and access controls
Trend analysis:
- Compliance posture improvement over time
- Finding closure rate trends
- Time-to-remediate trends
- Audit finding trends (fewer/more findings each cycle)
Write the artifact — append to
.singularskills/compliance/<project>/04-monitor.mdunder a## Compliance Reportingsection. Create the file with a# Monitor — <project>heading if it does not exist; if a## Compliance Reportingsection already exists, replace only that section. The section contains:- Executive Summary Template — leadership-ready compliance overview
- Operational Report Template — detailed compliance operations status
- Customer-Facing Report Template — trust page and customer communication content
- Reporting Cadence — schedule, audience, and distribution
- Trend Data — compliance posture trends and metrics
Output
The compliance reporting framework appended to .singularskills/compliance/<project>/04-monitor.md. Present a summary to the user highlighting:
- Overall compliance score — the weighted score computed as in
/compliance-compliance-score(each regulation's score from its01-assess/artifact; weights from00-scope.md, else equal) - RAG status across all regulations
- Key items for leadership attention
- Customer-facing compliance highlights
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-compliance-reporting","workflow":"compliance","phase":4,"project":"<project>","event":"finished","artifact":"04-monitor.md","note":""}.
This artifact is shared by every skill of phase 4 (Monitor). 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: Monitor
workflow: compliance
phase: 4
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Compliance Reporting section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is compliance-compliance-reporting).
End your section with ### Decisions and ### Open questions (one level under your ## Compliance Reporting 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.