SkillVaultskills Browse all 500 skills

Compliance · Version 1.2.0 · Reviewed 2026-08-02

Data Subject Request Designer

Make a defensible decision about system inventory and workflow design with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Designs access, correction, and deletion request handling that meets deadlines across every system.

₹99 one-time

Get this skill archive

What this skill helps you do

  • System inventory
  • Workflow design
  • Deadline management

How Data Subject Request Designer works

You provide

Requirements, data inventory, and evidence of current controls

It inspects

Requirement type and real implementation for system inventory

It decides

A workflow design gap list with owners and severity

You verify

One obligation traced end to end to its enforcing system

What it checks first

Data Subject Request Designer designs access, correction, and deletion request handling that meets deadlines across every system. Use it when the work involves System inventory, Workflow design, Deadline management.

  1. Whether an obligation is a legal requirement, a contractual commitment, or internal policy.
  2. Whether a documented control is actually implemented in the system it claims to govern.
  3. Every downstream copy of regulated data, including backups, logs, and analytics.
  4. Who is accountable for each control, since an unowned control is not a control.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, and warehouses.
  • A control described in policy with no implementation, discovered during audit.
  • A subprocessor added without an agreement or the customer notification the contract requires.
  • Retention defined but never enforced by an automated job.
  • Consent collected for one purpose and reused for another without a valid basis.

Answers it will reject

  • Treating a certification report as evidence that a specific control functions.
  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Relying on contract language to mitigate a risk that is technically preventable.

Decision rules it applies

  • Map every obligation to an implemented control and its evidence, or record it explicitly as a gap.
  • Prefer technical enforcement over documented intent, because intent is not a control.
  • Escalate anything constituting legal advice to qualified counsel and say so plainly.

Evidence it asks for

  • Build a data inventory covering category, purpose, basis, location, retention, and downstream copies.
  • Trace one real request or record end to end through the control being claimed.
  • Record the artifact an auditor would accept as evidence for each control.

The method inside

  1. Turn system inventory into explicit functional requirements and quality-attribute constraints.
  2. Model the critical path, state, trust, and failure boundaries that govern workflow design.
  3. Compare viable designs for deadline management against weighted constraints and operational ownership.
  4. Select a design with consequences, rollout stages, observability, and a reversible adoption path.

Deliverables

  • System inventory assessment
  • Workflow design decision and action plan
  • Deadline management verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We receive data deletion requests by email and handle them manually. It takes days and we are not confident.

Expected output

Manual handling fails on completeness rather than speed: the systems people forget are backups, analytics, and third-party processors. Build a system inventory with an owner and a deletion method for each, then automate the fan-out and collect evidence...

Boundaries and compatibility

Ideal for

  • System inventory: produce a decision or artifact grounded in supplied evidence.
  • Workflow design: produce a decision or artifact grounded in supplied evidence.
  • Deadline management: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.