All skills
experience-impact-modeler
ProfessionalRuntime top levelUse analysis-agent to map user-flow, interaction-state, accessibility, content, and recovery impact when experience behavior changes. Skip backend-only work with no experience effect and question-only requests.
- 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
- user flow change
- interaction state change
Do not use when
Anti-triggers — as binding as the triggers above
- backend only with no experience impact
- question only
Required inputs
What must be supplied before this skill can decide anything
- intent slice
- existing flow evidence
- read scope
Output contract
What this skill owes the next role
- flow evidence
- affected states
- experience constraints
Escalation signals
When this skill must hand the decision back
- scope, authority, or material risk exceeds the selected task contract
Related expertise
5 Layer 3 candidates may be loaded behind this skill — each only when the current task's evidence calls for it, never as a bundle.
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 |
|---|---|---|---|
| checklist.mddecision-checklist | A bounded review needs actor, entry, state, accessibility, analytics, and verification inventory | Full flow evidence, accessibility gates, or experiment proof decides closure | Analysis |
| experience-output-and-gates.mdtargeted | Closure depends on flow evidence, accessibility/recovery gates, analytics coupling, state-to-validation maps, or handoff fields | The body output contract is enough and evidence is not being closed | Analysis |
| index.mdindex | competing experience impact modeler references require dependency, conflict, or output-fragment selection | the experience impact modeler root or a task-named reference already resolves selection | Analysis |
| journey-risk-patterns.mdbenchmark-pattern | Journey risks involve destructive/sensitive flows, high-volume operational work, experiment instrumentation, stale prior-evidence claims, or proof limits | A local component UX check has no journey, analytics, or sensitive-flow risk | Analysis |