GDPR Compliance
Assess and implement GDPR compliance for "$ARGUMENTS". Conduct data mapping, evaluate DPIA requirements, define data subject rights procedures, and establish breach notification and cross-border transfer mechanisms.
See also /compliance-gdpr for a scored control-gap assessment of GDPR compliance area by area.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"skipped","artifact":"03-comply.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 3 (Comply) of the Legal Lifecycle workflow (legal); 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 legal 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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"refused","artifact":"03-comply.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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"started","artifact":"03-comply.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.md for risk, jurisdiction, and data practice context
- Read any existing draft or review artifacts in
.singularskills/legal/<project>/ for additional context
Conduct data mapping:
- What personal data is collected (categories and specific data elements)
- Where personal data is stored (systems, databases, third-party services, backups)
- Who processes the data (internal teams, processors, sub-processors)
- Retention periods per data category with justification
- Lawful basis per processing activity (consent, contract, legitimate interest, legal obligation, vital interest, public task)
- Data flows between systems and across borders
Assess need for DPIA:
- Evaluate against high-risk processing criteria (systematic monitoring, large-scale processing of special categories, automated decision-making with legal effects, innovative technologies, cross-border processing, vulnerable data subjects)
- If DPIA is required, draft DPIA including: description of processing, assessment of necessity and proportionality, risk assessment to individuals, measures to mitigate risks
Define data subject rights procedures:
- Right of access (Article 15) — procedure and response timeline (one month, extendable by two)
- Right to rectification (Article 16) — how inaccuracies are corrected
- Right to erasure (Article 17) — grounds for erasure, exceptions, process
- Right to restriction (Article 18) — when restriction applies, how data is marked
- Right to data portability (Article 20) — machine-readable format, direct transfer
- Right to object (Article 21) — direct marketing (absolute right), other processing (balancing test)
- Response timelines and escalation procedures
Breach notification process:
- Detection and assessment procedures
- 72-hour notification requirement to supervisory authority (Article 33)
- Notification to affected individuals without undue delay when high risk (Article 34)
- Content of notifications (nature of breach, categories and approximate number of data subjects, likely consequences, measures taken or proposed)
- Internal documentation requirements for all breaches regardless of notification
Cross-border transfer mechanisms:
- Adequacy decisions (current list of adequate countries)
- Standard Contractual Clauses (SCCs) — new 2021 modular SCCs
- Binding Corporate Rules (BCRs) for intra-group transfers
- Derogations for specific situations (explicit consent, contractual necessity)
- Transfer impact assessments where required
DPO appointment assessment:
- Evaluate whether DPO appointment is mandatory (public authority, core activities involve regular and systematic monitoring at large scale, core activities involve large-scale processing of special categories)
- If required, define DPO role, qualifications, and reporting structure
Article 30 records of processing:
- Draft records of processing activities for controller and processor roles
- Include all required fields (name and contact details, purposes, categories of data subjects and personal data, recipients, transfers, retention periods, security measures)
Write the artifact — append to .singularskills/legal/<project>/03-comply.md under a ## GDPR Compliance section. Create the file with a # Comply — <project> heading if it does not exist; if a ## GDPR Compliance section already exists, replace only that section. The section contains:
- Data Mapping — comprehensive inventory of personal data processing activities
- DPIA Assessment — determination and full DPIA if required
- Data Subject Rights Procedures — procedures for each right with timelines
- Breach Notification Plan — detection, assessment, and notification procedures
- Cross-Border Transfers — applicable mechanisms and safeguards
- DPO Assessment — appointment determination and role definition
- Records of Processing — Article 30 compliant records
- Compliance Gaps — identified gaps with remediation recommendations
Output
The GDPR compliance assessment appended to .singularskills/legal/<project>/03-comply.md. Present a summary to the user highlighting:
- Number of processing activities mapped
- Whether DPIA is required and key findings
- Data subject rights procedures defined
- Cross-border transfer mechanisms identified
- Critical compliance gaps requiring immediate attention
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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"finished","artifact":"03-comply.md","note":""}.
This artifact is shared by every skill of phase 3 (Comply). 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: Comply
workflow: legal
phase: 3
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## GDPR Compliance section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-gdpr-compliance).
End your section with ### Decisions and ### Open questions (one level under your ## GDPR Compliance 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>
1---2name: legal-gdpr-compliance3description: Analyze GDPR obligations legally — data mapping, lawful basis, DPIA and DPO needs, data subject rights procedures, breach notification, transfer mechanisms and Article 30 records. Use when the user asks how to legitimize EU data transfers, whether they need a DPIA or DPO, or what GDPR legally requires of them. Not for a scored control-gap assessment; see /compliance-gdpr.4metadata:5 source: https://skillmd.com/skills/bromso/legal-gdpr-compliance6 argument-hint: "[project] [--skip-checks]"7 workflow: legal8 phase: 39 artifact: 03-comply.md10---1112# GDPR Compliance1314Assess and implement GDPR compliance for "$ARGUMENTS". Conduct data mapping, evaluate DPIA requirements, define data subject rights procedures, and establish breach notification and cross-border transfer mechanisms.1516See also `/compliance-gdpr` for a scored control-gap assessment of GDPR compliance area by area.1718> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1920**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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"skipped","artifact":"03-comply.md","note":"<reason or \"none given\">"}`.2122## Prerequisites2324**Part of a workflow.** This skill is phase 3 (Comply) of the Legal Lifecycle workflow (`legal`); 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 `legal` 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.2526Run 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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"refused","artifact":"03-comply.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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"started","artifact":"03-comply.md","note":""}`.2728Check that `.singularskills/legal/<project>/00-assess.md` exists. If it does not exist, stop and tell the user:2930> "Run an Assess skill first (e.g. `/legal-risk-assessment <project>`) to generate the prerequisite assessment artifact."3132## Process33341. **Read inputs:**35 - Read `.singularskills/legal/<project>/00-assess.md` for risk, jurisdiction, and data practice context36 - Read any existing draft or review artifacts in `.singularskills/legal/<project>/` for additional context37382. **Conduct data mapping:**39 - What personal data is collected (categories and specific data elements)40 - Where personal data is stored (systems, databases, third-party services, backups)41 - Who processes the data (internal teams, processors, sub-processors)42 - Retention periods per data category with justification43 - Lawful basis per processing activity (consent, contract, legitimate interest, legal obligation, vital interest, public task)44 - Data flows between systems and across borders45463. **Assess need for DPIA:**47 - Evaluate against high-risk processing criteria (systematic monitoring, large-scale processing of special categories, automated decision-making with legal effects, innovative technologies, cross-border processing, vulnerable data subjects)48 - If DPIA is required, draft DPIA including: description of processing, assessment of necessity and proportionality, risk assessment to individuals, measures to mitigate risks49504. **Define data subject rights procedures:**51 - **Right of access** (Article 15) — procedure and response timeline (one month, extendable by two)52 - **Right to rectification** (Article 16) — how inaccuracies are corrected53 - **Right to erasure** (Article 17) — grounds for erasure, exceptions, process54 - **Right to restriction** (Article 18) — when restriction applies, how data is marked55 - **Right to data portability** (Article 20) — machine-readable format, direct transfer56 - **Right to object** (Article 21) — direct marketing (absolute right), other processing (balancing test)57 - Response timelines and escalation procedures58595. **Breach notification process:**60 - Detection and assessment procedures61 - 72-hour notification requirement to supervisory authority (Article 33)62 - Notification to affected individuals without undue delay when high risk (Article 34)63 - Content of notifications (nature of breach, categories and approximate number of data subjects, likely consequences, measures taken or proposed)64 - Internal documentation requirements for all breaches regardless of notification65666. **Cross-border transfer mechanisms:**67 - Adequacy decisions (current list of adequate countries)68 - Standard Contractual Clauses (SCCs) — new 2021 modular SCCs69 - Binding Corporate Rules (BCRs) for intra-group transfers70 - Derogations for specific situations (explicit consent, contractual necessity)71 - Transfer impact assessments where required72737. **DPO appointment assessment:**74 - Evaluate whether DPO appointment is mandatory (public authority, core activities involve regular and systematic monitoring at large scale, core activities involve large-scale processing of special categories)75 - If required, define DPO role, qualifications, and reporting structure76778. **Article 30 records of processing:**78 - Draft records of processing activities for controller and processor roles79 - Include all required fields (name and contact details, purposes, categories of data subjects and personal data, recipients, transfers, retention periods, security measures)80819. **Write the artifact** — append to `.singularskills/legal/<project>/03-comply.md` under a `## GDPR Compliance` section. Create the file with a `# Comply — <project>` heading if it does not exist; if a `## GDPR Compliance` section already exists, replace only that section. The section contains:8283 - **Data Mapping** — comprehensive inventory of personal data processing activities84 - **DPIA Assessment** — determination and full DPIA if required85 - **Data Subject Rights Procedures** — procedures for each right with timelines86 - **Breach Notification Plan** — detection, assessment, and notification procedures87 - **Cross-Border Transfers** — applicable mechanisms and safeguards88 - **DPO Assessment** — appointment determination and role definition89 - **Records of Processing** — Article 30 compliant records90 - **Compliance Gaps** — identified gaps with remediation recommendations9192## Output9394The GDPR compliance assessment appended to `.singularskills/legal/<project>/03-comply.md`. Present a summary to the user highlighting:95- Number of processing activities mapped96- Whether DPIA is required and key findings97- Data subject rights procedures defined98- Cross-border transfer mechanisms identified99- Critical compliance gaps requiring immediate attention100101**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":"legal-gdpr-compliance","workflow":"legal","phase":3,"project":"<project>","event":"finished","artifact":"03-comply.md","note":""}`.102103This artifact is shared by every skill of phase 3 (Comply). 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`).104105```yaml106---107skill: Comply108workflow: legal109phase: 3110project: <project>111started: <ISO timestamp>112finished: <ISO timestamp>113agent: <the agent you run in, or "unknown">114gate: <passed|skipped>115---116```117118Open your `## GDPR Compliance` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `legal-gdpr-compliance`).119120End your section with `### Decisions` and `### Open questions` (one level under your `## GDPR Compliance` heading, so the section stays one block), in this shape:121122```markdown123### Decisions124- <what was chosen> — <why> — <what was rejected>125126### Open questions127- <what the next phase or a reviewer must settle>128```