pm-privacy-requirements

Name: pm-privacy-requirements
Availability: InStock
Author: ljucask

Generate PII inventories, GDPR requirements, and pre-launch compliance action plans from domain models.

1|Updated May 28, 2026

Search Tags:#compliance #data protection #privacy #gdpr #pii inventory #privacy requirements

Ready to run

npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-privacy-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-privacy-requirements
Source: https://github.com/ljucask/pureinn-product-development/tree/main/skills/pm-privacy-requirements
Command: npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-privacy-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams identify personal data risks and convert domain information into actionable privacy requirements before development begins.

Core Features & Use Cases

PII Inventory Generation: Maps domain entities and attributes to personal data classifications, sensitivity levels, legal bases, retention needs, and third-party data flows.
Privacy Requirements Definition: Produces GDPR-oriented requirements covering consent, user rights, data minimization, retention, processing agreements, and privacy-by-design controls.
Compliance Action Planning: Creates a pre-launch GDPR action plan with owners, priorities, timelines, and open questions requiring legal review.
Use Case: A product manager preparing an AI-powered SaaS product can use this Skill after domain modeling to understand what user data is processed and what compliance work must happen before launch.

Quick Start

Use the pm-privacy-requirements skill to generate a PII Inventory, Privacy Requirements document, and GDPR Action Plan for my product based on the existing domain model.

Frequently Asked Questions about pm-privacy-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a PII inventory from a product domain model?▼

To generate a PII inventory, map your structured domain entities and attributes to personal data classifications, sensitivity levels, legal bases, retention needs, and third-party data flows.

What is privacy-by-design in product development?▼

Privacy-by-design is a framework that integrates data protection controls into product development early. It classifies data sensitivity, defines user rights, and ensures data minimization before launch.

How do I create a GDPR action plan for an AI-powered SaaS product?▼

Create a GDPR action plan by mapping processed user data to compliance requirements, producing an actionable pre-launch checklist with owners, priorities, timelines, and open legal review questions.

Do I need structured domain entities to define privacy requirements?▼

Yes, structured domain entities and attributes are required. They serve as the foundational input to classify data sensitivity, define privacy controls, and produce actionable governance artifacts.

What's the best way to translate product data risks into compliance plans?▼

The best way to translate data risks into compliance plans is to map domain data to personal information handling needs, classify sensitivity, and produce actionable governance artifacts for pre-launch preparation.

Why does GDPR compliance preparation require mapping third-party data flows?▼

GDPR compliance preparation requires mapping third-party data flows to accurately define processing agreements, identify external data sharing risks, and establish appropriate privacy controls.