메뉴
Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | journey-mapping |
| department | advocate |
| description | Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design). |
| version | 1 |
| triggers | ["user flow","journey","onboarding","experience","workflow","entry point","happy path","user story","persona"] |
Map complete user journeys with entry points, states, emotions, and decision points to ensure features serve real user needs.
Reads feature descriptions, user stories, and existing screen documentation for journey analysis. Does not modify files or execute code. Does not access user analytics data or production systems directly.
No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets.
How does the user discover or arrive at this feature:
Walk through step by step:
| Step | Screen/View | User Action | System Response | User Emotion | Notes |
|---|---|---|---|---|---|
| 1 | ... | ... | ... | ... | ... |
For each step capture:
Where users might:
Where can we exceed expectations:
Compaction resilience: If context was lost during a long session, re-read the Inputs section to reconstruct what feature is being mapped, check the Progress Checklist for completed steps, then resume from the earliest incomplete step.
| Step | Screen/View | User Action | System Response | User Emotion | Notes |
|---|---|---|---|---|---|
| ... | ... | ... | ... | ... | ... |
[Entry Point A] ──→ [Step 1] ──→ [Step 2] ──→ ...
[Entry Point B] ──→ [Step 1]
↓
[Error Path] ──→ [Recovery]
Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).
Use when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use schema-design) or API contract definition (use api-design).
Use when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).
Use when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use testing-strategy).
Use when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not use for regulatory gap analysis (use compliance-review) or audit logging design (use audit-trail-design).
Use when designing, evaluating, or versioning system prompts for LLM-powered features. Covers instruction structure, chain-of-thought patterns, output format constraints, few-shot example selection, and prompt versioning strategy. Do not use for RAG pipeline design (use rag-architecture) or AI evaluation frameworks (use ai-evaluation).