← ClaudeAtlas

cx-impactlisted

Create or update visual current-state or target-state customer journey maps (CJM), service blueprints and experience-process maps from product descriptions, documents, research or available code. Preserve requirements, observations, hypotheses and unknowns; deliver standalone interactive HTML, SVG export and reproducible source files. Compare current and target only when requested. Create separate quantitative sales funnels from supplied closed-cohort people counts. Also review a code change's impact on a user journey when requested.
shelasmax/cx-impact · ★ 0 · Web & Frontend · score 67
Install: claude install-skill shelasmax/cx-impact
# CX Impact Make a service understandable through a readable visual map. Work in the user's language and make the artifact the primary deliverable. A Git diff and customer research are not prerequisites. ## Establish the map's meaning Infer actor, goal, scenario boundary and date from the request and relevant sources. Ask only when missing information prevents a useful draft. Otherwise record the specific unknown, its affected stages and how it may change the path. Choose an explicit mode before authoring: - **Current / AS-IS:** the process as supported by available evidence. Declared rules remain declared; they do not prove actual behavior. - **Target / TO-BE:** the intended service. A request for «целевая картина» means target. Use requirements and proposals; do not turn it into an analysis of current code behavior. Code may inform feasibility or a clearly labelled constraint. - **Comparison:** create separate current and target scenarios only when the user requests a comparison. Supply explicit stage/node/lane correspondence for paired alignment; IDs alone never establish a match. Do not fill unknowns with target behavior. Choose the requested view, or one shared scenario for all three: - **CJM:** customer stages, goals, actions/channels, experience, barriers and improvements. - **Service blueprint:** customer evidence/actions, frontstage, backstage and support; explicit interaction and visibility boundaries. - **Experience-process map:** participant roles, actions,