Epic Journey

epic-journey

Load for UX-heavy epics to map user touchpoints, emotions, and flow before planning. Use when the epic significantly changes how users interact with the product. Run before epic-wireframes and epic-plan.

telum-ai/speck·0installs2stars

SKILL.md

Full skill instructions

The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).

User input:

$ARGUMENTS

Create a detailed user journey map for an epic to guide design and development decisions.

Context Gathering

Required Information:

Project name/ID (ask if not provided)
Epic name/ID (ask if not provided)
Load: project UX strategy, epic specification

If missing: "Which project and epic should I map the user journey for?"

Interactive Journey Mapping

Step 1: Understand Journey Context

Determine PROJECT_ID from epic path (e.g., specs/projects/001-myproject/epics/...).

Load required design context:

specs/projects/[PROJECT_ID]/ux-strategy.md → UX principles, voice/tone, emotional design goals
- Extract: Design principles, user personas, emotional journey targets, accessibility standards
- If missing: WARN "No UX strategy found. Run /project-ux for UX guidelines that inform journey mapping."
specs/projects/[PROJECT_ID]/design-system.md → Design tokens, interaction patterns
- Extract: Interaction patterns, feedback mechanisms, animation guidelines
- If missing: Note that touchpoint design will need alignment later

Load epic context:

Epic specification for scope
User personas from project spec (referenced in ux-strategy.md)

Step 2: Journey Discovery

The journey template (.speck/templates/epic/journey-template.md) needs specific inputs. Ask for what's missing:

Core journey questions:

"What triggers users to start this journey?"
"What tells them they've succeeded?"
"Which persona is this journey for?"

If stages unclear:

"Walk me through the main steps users take..."
"What are the key decision points?"

If emotions unknown:

"How do users typically feel at the start?"
"Where might they get frustrated?"
"What would delight them?"

Step 3: Pain Point Identification

For each stage identified, explore:

"What could go wrong here?"
"What might confuse users?"
"Where do they typically need help?"

Step 4: Opportunity Discovery

Based on pain points:

"How might we reduce this friction?"
"Where can we exceed expectations?"
"What would make this memorable?"

Step 5: Create Journey Map

Load template: .speck/templates/epic/journey-template.md
Create file at: specs/projects/[PROJECT_ID]/epics/[EPIC_ID]/user-journey.md
Fill systematically:
- Use discovered stages and emotions
- Document all pain points
- Include opportunity areas
- Add success metrics
- Mark unclear areas with [NEEDS CLARIFICATION]

Step 6: Review and Guide

Present what was created:

"I've mapped the user journey at [path]"
"Key pain points identified: [list]"
"Opportunities for delight: [list]"

Guide to next steps based on journey:

CRITICAL ORDERING RULE: For the canonical next steps, ALWAYS consult AGENTS.md at workspace root under ## 📋 The Speck Command Phases. Do NOT rely on individual skill files to determine phase ordering. Play Level (Sprint/Build/Platform) dictates the exact sequence.
If this UI epic requires layout design, the canonical next step is /epic-wireframes. For simpler or well-defined UIs, /epic-experience-chain is the core UI transition gate before planning.

The template contains the complete structure and guidance for journey documentation.

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/telum-ai/speck --skill epic-journey

View on GitHub

.cursor/skills/epic-journey/SKILL.md

epic-outline
DEPRECATED in Speck v7. Use /speck-skeptical-review + /speck-decision-log instead — they replace the outline pattern with structured tradeoff enumeration and lockable decisions. The v6 epic-outline pattern (research mapping) is now embedded in /epic-plan's just-in-time research step. This skill r...
0 installs
project-specify
Load at the very start of a new project when the user describes what they want to build, or to update an existing project.md. Produces project.md — must run before project-clarify, project-context, and all downstream project commands. FIRST ACTION after loading: read template at .speck/templates/...
0 installs
epic-constitution
Load when an epic has unique technical principles that extend or override the project constitution. Produces epic-level constitution.md — optional, skip when the project constitution is sufficient for this epic's concerns.
0 installs
oauth-implementation
Load when implementing OAuth 2.0 and OpenID Connect authentication. Applies when building social login, SSO, PKCE flows, or integrating with OAuth providers like Google, GitHub, Apple.
0 installs

More skills from telum-ai

telum-ai/speck

project-brainstorm

Load when a user has a vague idea, problem, or inspiration but isn't sure what to build. Use before /project-specify when the project concept needs crystallizing from loose thoughts into something concrete.

2 0

View

telum-ai/speck

docker-containerization

Load when using Docker for containerizing applications. Applies when creating Dockerfiles, docker-compose setups, multi-stage builds, or optimizing container images.

2 0

View

telum-ai/speck

visual-quality

Enforce visual design quality in every UI file. Fires for .tsx, .jsx, .vue, .svelte, and similar component files. Ensures implementations express the project's design personality rather than producing generic/boilerplate UI.

2 0

View

telum-ai/speck

project-clarify

Load after project.md exists to fill gaps through targeted Q&A. Use when project goals, target users, or scope feel underspecified. Run before project-context or project-architecture to prevent rework downstream.

2 0

View

telum-ai/speck

story-outline

DEPRECATED in Speck v7. Use /speck-skeptical-review + /speck-decision-log instead — they replace outline-style research mapping with structured alternative enumeration and decision locking. /story-plan now performs just-in-time research inline. This skill remains for v6 compatibility but redirect...

2 0

View

telum-ai/speck

offline-first-architecture

Load when building offline-first applications that work without network connectivity. Applies when implementing local storage, sync queues, conflict resolution, or background sync.

2 0

View

telum-ai/speck

project-constitution

Load (Platform play level only) to define technical principles and architectural guardrails for the project. Produces constitution.md — optional but valuable when a team needs explicit coding standards, governance rules, or non-negotiable constraints. FIRST ACTION after loading: read template at ...

2 0

View

telum-ai/speck

posthog-integration

Load when integrating PostHog for product analytics and feature flags. Applies when implementing event tracking, A/B testing, session replay, or funnel analysis.

2 0

View

telum-ai/speck

project-validate

Load when all epics are validated and /audit has run for the project. Verifies the project meets its original vision and product-contract.md paid promise. Runs end-to-end JTBD smoke test via /larp across all personas. Declares a project-level readiness state. Produces project-validation-report.md...

2 0

View

telum-ai/speck

story-scan

Load for brownfield stories where existing code must be understood before planning. Use when a story extends, modifies, or integrates with significant existing functionality. Produces codebase-scan.md — skip for fully greenfield stories. FIRST ACTION after loading: read template at .speck/templat...

2 0

View

telum-ai/speck

serverless-architecture

Load when building serverless applications with AWS Lambda, Vercel Functions, or Cloudflare Workers. Applies when implementing FaaS patterns, managing cold starts, or optimizing serverless costs.

2 0

View

telum-ai/speck

epic-analyze

Load after epic-tech-spec.md and epic-breakdown.md exist — quality check for consistency and completeness before any story work begins. Catches spec drift and missing coverage between the tech spec and story breakdown. FIRST ACTION after loading: read template at .speck/templates/epic/epic-analys...

2 0

View