القائمة
Designs lifecycle, retention, archival, deletion, legal hold and disposal controls. Use when defining data retention policies, archival strategy, or compliant deletion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Use when reviewing plans, recommendations, prioritisation, risk registers, retrospectives or agent outputs for judgement distortion from cognitive bias — not for checking whether an argument's premises validly support its conclusion.
Use when evaluating whether premises in plans, ADRs, reviews, security justifications or agent recommendations validly support their conclusions — for logical fallacies, not judgement distortion from cognitive bias.
Use when a coding agent needs robust problem solving, explicit decomposition, alternative-path exploration, program-aided reasoning, ReAct loops, or self-correction.
Use when generated code, plans, tests, prompts or architecture need critique, repair and verification before completion; especially for coding tasks requiring self-review, test-driven repair or quality gates.
Identifies risks, scores likelihood and impact, selects treatment, assigns owners and review cadence. Use when building or updating a risk register, treating agent autonomy risks, or deciding mitigate, transfer, accept or avoid.
| name | data-lifecycle-and-retention-management |
| description | Designs lifecycle, retention, archival, deletion, legal hold and disposal controls. Use when defining data retention policies, archival strategy, or compliant deletion. |
Use for datasets, products, logs, events, metadata, quarantine stores and refined datasets with retention obligations.
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Apply DAMA-DMBOK2-style separation of data governance, architecture, modelling, security, integration/interoperability, master/reference data, metadata and quality. For cloud/shared data, apply CDMC-style expectations: ownership, classification, entitlement/access evidence, lineage/provenance, lifecycle/retention, quality controls and auditable evidence.
Do not keep data indefinitely because deletion is inconvenient.
