All skills
transaction-consistency
FoundationJIT onlyUse with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.
- Group
- Data & middleware
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design transaction boundaries isolation consistency locking and conflict handling
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local transaction consistency 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
- consistency plan with transaction scope isolation conflicts and tests
Escalation signals
When this skill must hand the decision back
- Weak consistency causes lost updates stale reads and broken invariants
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 | invariant anomaly or effect ordering leaves consistency mechanisms unresolved | actual atomic boundary selects one proven consistency mechanism | AnalysisTask |
| checklist.mddecision-checklist | change affects atomic writes isolation conflicts remote effects or recovery | no transaction invariant or partial-failure behavior changes | AnalysisTask |
| evidence-patterns.mdevidence-pattern | isolation ordering idempotency or reconciliation claims need fresh proof | current handlers datastore tests and artifacts prove each claim | AnalysisTask |