القائمة
Governs event ownership, classification, metadata, lineage, quality and lifecycle. Use when governing shared event catalogues, schemas, or stream ownership.
التثبيت باستخدام 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 | event-governance-and-lineage |
| description | Governs event ownership, classification, metadata, lineage, quality and lifecycle. Use when governing shared event catalogues, schemas, or stream ownership. |
Use when events are shared, reused, regulated or business-critical.
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Apply event-driven best practice: business event semantics, producer/consumer ownership, schema contracts, compatibility, ordering, partitioning, idempotency, replay, retention, lineage, observability and operational SLOs.
Do not rely on tribal knowledge for event meaning.
For each shared event, capture owner, business definition, source capability, producer, consumers, schema version, classification, retention, quality checks, lineage links and support contact. A catalogue entry is not complete until consumers can understand meaning, sensitivity, replay constraints and who approves breaking changes.
