generate-gdpr-ropa

To generate a GDPR Article 30 ROPA, this Skill scans MODULE_MANIFEST.md and BEHAVIORAL_CONTRACTS.md files to identify data processing activities, drafts the documentation, and outputs it for legal review. It automates mapping data flows to processing activities across your repository.

Documenting data processing activities for a GDPR audit is best handled by scanning repository context files like MODULE_MANIFEST.md to auto-populate data flows. The tool then conducts an interview workflow for fields requiring human legal judgment.

Yes, you can draft ROPA documentation for a single module by using the --module path/to/module command. This allows module-specific generation of data processing activities instead of requiring a full repository-wide scan.

You need MODULE_MANIFEST.md and BEHAVIORAL_CONTRACTS.md context files to automate GDPR ROPA drafting. The Skill scans these specific files across the codebase to identify data processing activities and map data flows for the compliance package.

The generated ROPA draft requires legal review because it outputs a preliminary compliance document to docs/compliance/gdpr-ropa-YYYY-MM-DD.md. It uses an interview-driven workflow to gather human judgment on legal basis, purpose, and international transfers, but final validation is necessary.