What problem does it solve? Drafting a Privacy Impact Assessment from scratch is slow and inconsistent — teams struggle to know whether a PIA is legally required, what questions to ask the product team, and how to match the organization's established format. This Skill structures the entire PIA workflow so the output looks like the assessments your team already produces. ## Core Features & Use Cases - Trigger Analysis: Determines whether a PIA is actually needed by checking house trigger criteria and researching mandatory-assessment triggers under GDPR, CCPA/CPRA, and other applicable regimes with cited primary sources. - Structured Intake: Guides a conversational intake with the product team covering data categories, lawful bases, access, retention, and risk scenarios. - House-Format Output: Writes the PIA using the structure learned from your seed PIA, including lawful basis tables, data flow, privacy policy consistency checks, risk/mitigation tables, and sign-off routing. - Use Case: A product manager proposes a location-sharing feature. Run the Skill to confirm a DPIA is triggered under GDPR, intake the data flow details, and produce a draft PIA with conditions and named owners ready for attorney sign-off. ## Quick Start Ask the assistant to write a privacy impact assessment for your new feature, for example by saying: write a PIA for the location sharing feature.
