All skills
data-side-effect-flow-tracing
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when persistence, cache, events, external I/O, or compensation may hide or misorder side effects; skip unchanged flows.
- Group
- Engineering workflow
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- data side effect flow, input validation, mapping, policy, mutation, transaction, persistence, cache, event, external IO, logging, metrics, file IO, clock, random, env, outbox, publish after commit, idempotency, compensation, hidden side effect, mapper, getter
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local data side effect flow tracing 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
- side-effect flow with authoritative inputs, mutations and effects, order and commit boundaries, repeat and unknown outcomes, failure and cleanup paths, evidence limits, and residual owners
Escalation signals
When this skill must hand the decision back
- Hidden side effects in mappers getters policies or domain objects break transaction ordering cache consistency idempotency and testability
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 | Ordering, compensation, nondeterminism, or publication mechanisms need selection. | The affected path is pure and side-effect free. | TaskReviewAnalysis |
| checklist.mddecision-checklist | Flow crosses persistence, cache, events, external IO, or retries. | No mutation or external interaction is reachable. | TaskReviewAnalysis |
| evidence-patterns.mdevidence-pattern | Flow safety depends on fresh call-order and failure-path evidence. | No effect-ordering or purity claim awaits proof. | TaskReviewAnalysis |