All skills
privacy-data-lifecycle
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when personal-data purpose, retention, deletion, sharing, telemetry, or provider handling changes; skip legal-only work.
- Group
- Security & privacy
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- personal or sensitive data collection derivation storage observation retention deletion export correction sharing de-identification provider or region change
Do not use when
Anti-triggers — as binding as the triggers above
- no personal or sensitive data change or only authentication secret cryptographic legal or one client local-data API
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- Privacy engineering decision with data inventory, classification, purpose, and minimization; retention and deletion map; individual-facing operations; telemetry, de-identification, provider, and regional handling; authority gaps, evidence, and proof limits.
Escalation signals
When this skill must hand the decision back
- data purpose authority lifecycle owner or provider handling remains unresolved
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| data-lifecycle-controls.mdtargeted | A named data flow has unresolved collection purpose minimization retention deletion backup export correction telemetry provider or regional handling, within one store or across processing boundaries | One bounded data flow already has an accepted purpose and complete lifecycle contract | AnalysisTaskReview |
| de-identification-and-provider-controls.mdtargeted | De-identification linkage sharing provider or release-model choices remain open | No de-identification linkage sharing provider or release-model decision remains open | AnalysisTaskReview |