All skills
domain-event-modeling
FoundationJIT onlyanalysis-agent/task-agent: use when commit timing, payloads, schema, ordering, idempotency, or retry changes; skip when no domain-event decision is required.
- Group
- Domain modeling
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- model domain events producers consumers payloads timing and consistency expectations
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local domain event modeling decision is required
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
- domain-event decision with fact meaning, producer and commit boundary, subject and payload contract, identity and ordering, compatibility, consumer responsibilities, failure evidence, and residual owners
Escalation signals
When this skill must hand the decision back
- Incorrect events create duplicate effects missed notifications and stale projections
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 |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Commit, schema, ordering, replay, or payload mechanisms remain open. | The signal is not a durable domain fact. | AnalysisTask |
| checklist.mddecision-checklist | Event changes producer commits, consumers, retries, or sensitive payloads. | No domain event contract or delivery behavior changes. | AnalysisTask |
| event-evidence-freshness.mdevidence-pattern | Event approval depends on fresh topology, contracts, or replay results. | No event-catalog or consumer claim is being accepted. | AnalysisTask |