Regulatory Landscape
Map the full regulatory landscape for "$ARGUMENTS". Identify every applicable regulation based on where the business operates, what data it processes, what industries its customers serve, and what certifications those customers require.
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-regulatory-landscape","workflow":"compliance","phase":0,"project":"<project>","event":"skipped","artifact":"00-scope.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 0 (Scope) 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, unless the user named this skill, ask one question, since this is the first phase of its workflow: "Just this step, or the whole GRC Lifecycle workflow?" End your turn and wait; on the whole workflow, hand off the same way; on just this step, continue here.
Recall. Before you ask the user anything, look for what this repository already holds about <project>: if a tool is available whose description says it searches or maps this repository (a memory or repo-map server such as repo_map or entities), query it for <project> and this phase's subject and read what it returns, keeping only results from this repository; in every case also list .singularskills/*/<project>/ and read the Decisions and Open questions of any artifact there, and the lines of .singularskills/log.jsonl whose project is <project>. After your section's italic line, add a ### Recalled subsection of at most ten lines naming what you found and where (path or tool), or the single line Nothing recalled: no earlier artifacts, log lines or memory results for <project>. Ask the user only what this did not answer. The trail's shape is described in references/memory/trail.md, bundled with this skill.
Before you start work, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-regulatory-landscape","workflow":"compliance","phase":0,"project":"<project>","event":"started","artifact":"00-scope.md","note":""}.
None — this is a Phase 0 (Scope) skill.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference
- Read
Jurisdiction mapping:
- Identify all jurisdictions where the business operates (headquarters, offices, data centers, customers)
- Map each jurisdiction to its regulatory requirements (EU, US federal, US state, UK, APAC, etc.)
- Note cross-border data transfer implications
Data classification:
- Identify data types processed (PII, PHI, PCI, financial data, children's data, biometric data, etc.)
- Map each data type to regulations that govern it
- Note data residency and sovereignty requirements
Industry and customer analysis:
- Identify industries the business serves (healthcare, finance, government, education, etc.)
- Map industry-specific regulations (HIPAA, PCI DSS, FedRAMP, FERPA, etc.)
- Document certifications customers require or request in sales cycles
Regulation inventory:
- Create a comprehensive regulation inventory table with columns: regulation name, jurisdiction, data types covered, industry applicability, mandatory vs. customer-driven, enforcement status
- Map each regulation to applicability criteria specific to ""
- Flag regulations with upcoming enforcement dates or recent changes
Write the artifact — append to
.singularskills/compliance/<project>/00-scope.mdunder a## Regulatory Landscapesection. Create the file with a# Scope — <project>heading if it does not exist; if a## Regulatory Landscapesection already exists, replace only that section. The section contains:- Jurisdiction Map — where the business operates and applicable jurisdictions
- Data Type Inventory — data types processed and governing regulations
- Industry Requirements — sector-specific regulations and customer demands
- Regulation Inventory Table — full list of applicable regulations with applicability criteria
- Cross-Border Considerations — data transfer and sovereignty requirements
Output
The regulatory landscape analysis appended to .singularskills/compliance/<project>/00-scope.md. Present a summary to the user highlighting:
- Total number of applicable regulations identified
- Top regulations by business impact
- Any surprising applicability findings
- Recommended next step: run
/compliance-compliance-priorities <project>
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-regulatory-landscape","workflow":"compliance","phase":0,"project":"<project>","event":"finished","artifact":"00-scope.md","note":""}.
This artifact is shared by every skill of phase 0 (Scope). 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 none, as this phase has no gate); if it already exists, leave the block alone except to update finished.
---
skill: Scope
workflow: compliance
phase: 0
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: none
---
Open your ## Regulatory Landscape section with one italic line, *<skill name> · <ISO timestamp> · gate: none* (your skill name is compliance-regulatory-landscape).
End your section with ### Decisions and ### Open questions (one level under your ## Regulatory Landscape 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.