All skills
domain-impact-modeler
ProfessionalRuntime top levelUse analysis-agent to identify domain ownership, invariants, state transitions, and cross-context effects when rules change or ownership is unclear. Skip presentation-only or question-only work with no domain behavior.
- Group
- Impact, domain and architecture
- Routing mode
- evidence-only
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- business invariant change
- domain ownership unclear
Do not use when
Anti-triggers — as binding as the triggers above
- presentation only with no domain behavior
- question only
Required inputs
What must be supplied before this skill can decide anything
- intent slice
- domain source evidence
- owning module candidates
Output contract
What this skill owes the next role
- owning module
- domain invariants
- rejected locations
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
9 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.
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 |
|---|---|---|---|
| business-invariant-evidence.mdevidence-pattern | Business vocabulary, state transitions, calculations, or forbidden outcomes need explicit invariant proof | No domain invariant changes | Analysis |
| checklist.mddecision-checklist | Aggregate, rule, event, permission, transition, audit, or consistency surfaces need a compact coverage check | The current source and tests already establish every relevant surface | Analysis |
| evidence-patterns.mdevidence-pattern | A domain rule needs source-to-test, event-consumer, owner, freshness, or residual-risk evidence | The root output contract is sufficient for the bounded decision | Analysis |
| index.mdindex | competing domain impact modeler references require dependency, conflict, or output-fragment selection | the domain impact modeler root or a task-named reference already resolves selection | Analysis |