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.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Prerequisites
Check that .metapowers/legal/$ARGUMENTS/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal:risk-assessment $ARGUMENTS) to generate the prerequisite assessment artifact."
If the user passes --skip-checks, bypass this check and log the skip to .metapowers/legal/$ARGUMENTS/skip-log.md with a timestamp and the reason "Prerequisite check skipped for gdpr-compliance".
Process
Read inputs:
- Read
.metapowers/legal/$ARGUMENTS/00-assess.md for risk, jurisdiction, and data practice context
- Read any existing draft or review artifacts in
.metapowers/legal/$ARGUMENTS/ 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 to .metapowers/legal/$ARGUMENTS/03-comply.md with frontmatter:
---
description: GDPR compliance assessment for $ARGUMENTS
---
Include sections:
- 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 written to .metapowers/legal/$ARGUMENTS/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
1---2name: gdpr-compliance3description: Assess and implement GDPR compliance — data mapping, DPIA, DPA4---56# GDPR Compliance78Assess 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.910> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1112## Prerequisites1314Check that `.metapowers/legal/$ARGUMENTS/00-assess.md` exists. If it does not exist, stop and tell the user:1516> "Run an Assess skill first (e.g. `/legal:risk-assessment $ARGUMENTS`) to generate the prerequisite assessment artifact."1718If the user passes `--skip-checks`, bypass this check and log the skip to `.metapowers/legal/$ARGUMENTS/skip-log.md` with a timestamp and the reason "Prerequisite check skipped for gdpr-compliance".1920## Process21221. **Read inputs:**23 - Read `.metapowers/legal/$ARGUMENTS/00-assess.md` for risk, jurisdiction, and data practice context24 - Read any existing draft or review artifacts in `.metapowers/legal/$ARGUMENTS/` for additional context25262. **Conduct data mapping:**27 - What personal data is collected (categories and specific data elements)28 - Where personal data is stored (systems, databases, third-party services, backups)29 - Who processes the data (internal teams, processors, sub-processors)30 - Retention periods per data category with justification31 - Lawful basis per processing activity (consent, contract, legitimate interest, legal obligation, vital interest, public task)32 - Data flows between systems and across borders33343. **Assess need for DPIA:**35 - 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)36 - If DPIA is required, draft DPIA including: description of processing, assessment of necessity and proportionality, risk assessment to individuals, measures to mitigate risks37384. **Define data subject rights procedures:**39 - **Right of access** (Article 15) — procedure and response timeline (one month, extendable by two)40 - **Right to rectification** (Article 16) — how inaccuracies are corrected41 - **Right to erasure** (Article 17) — grounds for erasure, exceptions, process42 - **Right to restriction** (Article 18) — when restriction applies, how data is marked43 - **Right to data portability** (Article 20) — machine-readable format, direct transfer44 - **Right to object** (Article 21) — direct marketing (absolute right), other processing (balancing test)45 - Response timelines and escalation procedures46475. **Breach notification process:**48 - Detection and assessment procedures49 - 72-hour notification requirement to supervisory authority (Article 33)50 - Notification to affected individuals without undue delay when high risk (Article 34)51 - Content of notifications (nature of breach, categories and approximate number of data subjects, likely consequences, measures taken or proposed)52 - Internal documentation requirements for all breaches regardless of notification53546. **Cross-border transfer mechanisms:**55 - Adequacy decisions (current list of adequate countries)56 - Standard Contractual Clauses (SCCs) — new 2021 modular SCCs57 - Binding Corporate Rules (BCRs) for intra-group transfers58 - Derogations for specific situations (explicit consent, contractual necessity)59 - Transfer impact assessments where required60617. **DPO appointment assessment:**62 - 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)63 - If required, define DPO role, qualifications, and reporting structure64658. **Article 30 records of processing:**66 - Draft records of processing activities for controller and processor roles67 - Include all required fields (name and contact details, purposes, categories of data subjects and personal data, recipients, transfers, retention periods, security measures)68699. **Write the artifact** to `.metapowers/legal/$ARGUMENTS/03-comply.md` with frontmatter:7071 ```72 ---73 description: GDPR compliance assessment for $ARGUMENTS74 ---75 ```7677 Include sections:78 - **Data Mapping** — comprehensive inventory of personal data processing activities79 - **DPIA Assessment** — determination and full DPIA if required80 - **Data Subject Rights Procedures** — procedures for each right with timelines81 - **Breach Notification Plan** — detection, assessment, and notification procedures82 - **Cross-Border Transfers** — applicable mechanisms and safeguards83 - **DPO Assessment** — appointment determination and role definition84 - **Records of Processing** — Article 30 compliant records85 - **Compliance Gaps** — identified gaps with remediation recommendations8687## Output8889The GDPR compliance assessment written to `.metapowers/legal/$ARGUMENTS/03-comply.md`. Present a summary to the user highlighting:90- Number of processing activities mapped91- Whether DPIA is required and key findings92- Data subject rights procedures defined93- Cross-border transfer mechanisms identified94- Critical compliance gaps requiring immediate attention