brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
gdpr-audit-prepGDPR audit-prep playbook: sprint to prepare for a supervisory authority inquiry, DPA audit, or internal review. Use when an audit is scheduled, when readiness gaps surface, or when ROPA (Records of Processing Activities) needs completion.
Independent GitHub snapshot · Automated classification · Original documentation governs
Operational playbook for GDPR audit preparation — whether triggered by a Data Protection Authority (DPA) inquiry, customer-side DPA review, internal compliance audit, or annual self-assessment.
When to use this skill vs. gdpr-dsgvo-expert:
| Situation | Skill applies |
|---|---|
| Supervisory authority inquiry received | Yes — start immediately; engage DPO |
| Customer DPA audit / questionnaire | Yes — scripts/gdpr_readiness_score.py first |
| Annual internal GDPR audit | Yes — standard sprint |
| ROPA needs rapid update | Yes — scripts/ropa_completeness_checker.py |
| New high-risk processing → DPIA needed | Use ra-qm-team/gdpr-dsgvo-expert for DPIA design |
Week 1: ROPA review + DPO engagement plan
Week 2: Gap remediation (policies, notices, technical)
Week 3: Evidence compilation + walkthroughs
Week 4: Audit week / submission
Weeks 1-2: ROPA update + gap identification
Weeks 3-5: Gap closure (DPAs, notices, security, retention)
Weeks 6-7: Evidence + walkthroughs
Week 8: Audit
Weeks 1-2: Inquiry analysis + response strategy + DPO engagement
Weeks 3-8: Targeted evidence collection + remediation
Weeks 9-10: Formal response drafting + legal review
Weeks 11-12: Submission + ongoing dialogue
See references/gdpr-pre-audit-checklist.md for the full pre-audit punch list and references/dpo-engagement-playbook.md for DPO-coordinated audit response.
Every processing activity documented:
Audit gap: ROPA incomplete, stale, or missing for processing activities surfaced during audit.
Before running the audit-prep, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the readiness assessment.
python3 scripts/gdpr_readiness_score.py --config gdpr-controls.yamlpython3 scripts/ropa_completeness_checker.py --ropa ropa.yaml| Script | Purpose |
|---|---|
scripts/gdpr_readiness_score.py | Score current state per GDPR area; identify gaps |
scripts/ropa_completeness_checker.py | Validate ROPA structure and completeness per Article 30 |
ra-qm-team/gdpr-dsgvo-expert — deep GDPR program managementra-qm-team/audit-prep/compliance-readiness — multi-framework readiness (GDPR + ISO 27001 + SOC 2)ra-qm-team/ccpa-cpra-privacy-expert — US privacy counterpartra-qm-team/audit-prep/ai-act-readiness — EU AI Act overlay for AI processing