User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages.
Install Biz Customer Journey
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install asgard-ai-platform/skills biz-customer-journey --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/biz-customer-journey .claude/skills/biz-customer-journey && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .claude/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journeyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install asgard-ai-platform/skills biz-customer-journey --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/biz-customer-journey .agents/skills/biz-customer-journey && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .agents/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install asgard-ai-platform/skills biz-customer-journey --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/biz-customer-journey .cursor/skills/biz-customer-journey && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .cursor/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/asgard-ai-platform/skills.git --path biz-customer-journey--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install asgard-ai-platform/skills biz-customer-journey --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/biz-customer-journey .gemini/skills/biz-customer-journey && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .gemini/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install asgard-ai-platform/skills biz-customer-journeyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/biz-customer-journey .github/skills/biz-customer-journey && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .github/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install asgard-ai-platform/skills biz-customer-journey --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/biz-customer-journey .opencode/skills/biz-customer-journey && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "biz-customer-journey" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/biz-customer-journey into .opencode/skills/biz-customer-journey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "biz-customer-journey", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
biz-customer-journey- GitHub stars
- 242
- Token cost
- ~1.8k tokens
- SKILL.md length
- 686 words
- Files
- 3 (incl. references)
- Skills in repo
- 207
- Repo updated
- First seen
- Licence
- MIT
At a glance
Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages.
- Works in 4 steps: Define the Persona → Map Touchpoints per Stage → Identify Moments of Truth → …
- The user needs to understand the customer experience end-to-end
- SKILL.md covers Overview, When to Use, Framework and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Biz Customer Journey is an agent skill from asgard-ai-platform/skills. Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages. Use this skill when the user needs to understand the customer experience end-to-end, identify drop-off points, optimize touchpoints, or improve conversion — even if they say 'where are we losing customers', 'what's our funnel look like', or 'map the user experience'.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `examples/sample_scenario.md` and `references/service-blueprint.md`).
It sits in Product & Project Management, covering Customer journey mapping. The repository describes itself as: 301 open-source coding agent skills across 22 domains — methodology, judgment & gotchas packaged as Claude Agent Skills for the Asgard AI Platform. The licence is MIT.
When your agent uses it
- The user needs to understand the customer experience end-to-end
- Identify drop-off points
- Optimize touchpoints
- Improve conversion — even if they say where are we losing customers
Example prompts
- “where are we losing customers”
- “s our funnel look like”
- “map the user experience”
- “/biz-customer-journey”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4e7f4f8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Biz Customer Journey loads about 1.8k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 686 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 686 words, ~1,818 tokens.
Download SKILL.mdSave it as
.claude/skills/biz-customer-journey/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- biz-customer-journey
- description
- Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages. Use this skill when the user needs to understand the customer experience end-to-end, identify drop-off points, optimize touchpoints, or improve conversion — even if they say 'where are we losing customers', 'what's our funnel look like', or 'map the user experience'.
- metadata.category
- WP-14 商學院—行銷
- metadata.tags
- marketing, customer-journey, experience-design
Customer Journey Mapping
Overview
Customer Journey Mapping visualizes the entire experience a customer has with a brand — from first awareness through post-purchase advocacy. It identifies touchpoints, emotions, pain points, and opportunities at each stage. The goal is to find and fix where customers get stuck, frustrated, or leave.
When to Use
Trigger conditions:
- User wants to improve conversion rates across the funnel
- User needs to understand where customers drop off
- User designing or redesigning a customer experience
- User asks "where are we losing customers?" or "what's the user experience like?"
When NOT to use:
- For market segmentation → use STP
- For product feature decisions → use Jobs to Be Done
- For one-time strategic analysis → use SWOT
Framework
IRON LAW: Map the Customer's Reality, Not Your Ideal
The journey map must reflect what customers ACTUALLY experience, not what
you designed or intended. If customers Google your brand and find negative
reviews (reality), don't map "customer visits our website" (ideal).
Base the map on data: analytics, customer interviews, support tickets,
heatmaps — not internal assumptions.IRON LAW: Every Touchpoint Needs an Emotion
A journey map without emotions is a process diagram. At every touchpoint,
note the customer's emotional state: confident, confused, frustrated,
delighted. Emotions predict behavior better than process steps.The Five Stages
1. Awareness — Customer realizes they have a need or discovers your brand
- Touchpoints: ads, social media, word-of-mouth, search results, content
- Key question: "How do they first encounter us?"
2. Consideration — Customer evaluates options and compares alternatives
- Touchpoints: website, reviews, comparisons, demos, sales conversations
- Key question: "What information do they seek and where?"
3. Decision — Customer chooses and purchases
- Touchpoints: checkout, pricing page, sales closing, contract signing
- Key question: "What friction exists at the purchase moment?"
4. Usage — Customer uses the product/service
- Touchpoints: onboarding, product interaction, support, documentation
- Key question: "Does the experience match the promise?"
5. Advocacy — Customer recommends (or warns against) the brand
- Touchpoints: reviews, referrals, social sharing, community
- Key question: "What triggers them to recommend us — or not?"
Step 1: Define the Persona
Who is this journey for? Use the target segment from STP:
- Name, demographics, goals, pain points
- The more specific the persona, the more actionable the map
Step 2: Map Touchpoints per Stage
For each stage, list:
- Touchpoints: Every interaction point (physical, digital, human)
- Actions: What the customer does
- Emotions: How the customer feels (😊 positive / 😐 neutral / 😤 negative)
- Pain points: What frustrates or blocks them
- Opportunities: How to improve the experience
Step 3: Identify Moments of Truth
Find the 2-3 critical moments that disproportionately impact the overall experience:
- First impression: The first touchpoint sets expectations
- Friction peak: The highest-pain-point moment
- Delight opportunity: Where a small improvement creates outsized positive impact
Step 4: Prioritize Improvements
Rank improvements by: Impact on customer satisfaction × Feasibility × Cost. Fix the highest-impact pain points first.
Output Format
# Customer Journey Map: {Product/Service}
## Persona
- Name: {persona name}
- Profile: {segment description}
- Goal: {what they're trying to achieve}
## Journey Map
| Stage | Touchpoints | Actions | Emotion | Pain Points | Opportunities |
|-------|------------|---------|---------|-------------|---------------|
| Awareness | {list} | {what they do} | 😊/😐/😤 | {friction} | {improvement} |
| Consideration | ... | ... | ... | ... | ... |
| Decision | ... | ... | ... | ... | ... |
| Usage | ... | ... | ... | ... | ... |
| Advocacy | ... | ... | ... | ... | ... |
## Moments of Truth
1. **{moment}** — {why this is critical}
2. **{moment}** — {why this is critical}
## Priority Improvements
1. {Stage} → {specific improvement} — Impact: High, Effort: Low
2. ...Examples
Show full SKILL.md (313 more words)Show less
Correct Application
Scenario: Journey for a Taiwanese food delivery app (persona: 30-year-old office worker ordering lunch)
| Stage | Touchpoints | Emotion | Pain Point |
|---|---|---|---|
| Awareness | Colleague mentions app during lunch discussion | 😊 Curious | None — organic discovery |
| Consideration | Downloads app, browses restaurants, reads reviews | 😐 → 😤 | Too many choices, no "nearby + fast" filter |
| Decision | Selects restaurant, adds items, sees delivery fee + minimum order | 😤 | Delivery fee NT$60 feels expensive for a NT$120 lunch; minimum order forces buying more than needed |
| Usage | Waits for delivery, receives food, eats | 😊 → 😐 | Food arrives in 35 min (app said 25), packaging leaked |
| Advocacy | Doesn't refer friends | 😐 | No referral incentive; experience was "okay, not great" |
Moment of Truth: Decision stage — the delivery fee shock causes 40% cart abandonment (data-backed ✓).
Incorrect Application
What went wrong:
- Map shows "Customer visits website → Customer signs up → Customer makes purchase" → This is a process flow, not a journey map. No emotions, no pain points. Violates Iron Law: every touchpoint needs an emotion.
- Awareness stage shows "Customer sees our billboard campaign" when the company doesn't have billboards → Mapping the ideal, not reality. Violates Iron Law: map reality.
Gotchas
- Backstage vs frontstage: Customers don't see your internal processes. Map what the customer experiences, not your operations. "Order routed to kitchen" is backstage; "Customer sees 'preparing your order' notification" is frontstage.
- Multiple personas = multiple maps: Different segments have different journeys. A B2B enterprise buyer's journey is completely different from a self-serve SMB user. Don't combine them.
- Post-purchase is often ignored: Most teams map Awareness → Decision thoroughly but skip Usage and Advocacy. Retention and referral happen post-purchase.
- Data over intuition: "We think customers feel frustrated at checkout" is a hypothesis. "Cart abandonment rate is 65% at the delivery fee screen" is evidence. Use data wherever possible.
- Journey maps expire: Customer behavior changes. A map from 2023 may be obsolete by 2025. Revisit quarterly for fast-moving products.
References
- For service blueprint extension (adding backstage operations), see
references/service-blueprint.md
© asgard-ai-platform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in biz-customer-journey of asgard-ai-platform/skills.
- SKILL.md
- examples/sample_scenario.md
- references/service-blueprint.md
Open the folder on GitHubat commit 4e7f4f8
Compare with similar skills
Biz Customer Journey next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Biz Customer Journey this skillasgard-ai-platform/skills | 242 | — | ~1.8k | Automated safety check: Pass | MIT | |
| User Story Mappingdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| QA Critical UXfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Journey Map Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.7k | Automated safety check: Pass | Custom licence | |
| Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~7.9k | Automated safety check: Pass | None |
Similar skills
QA Critical UX
fastrepl/anarlog
QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
Customer Journey Map Builder
deanpeters/Product-Manager-Skills
Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.
Super Product Owner
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…
Attribution Analysis Modeling
liangdabiao/claude-data-analysis-ultra-main
Perform multi-touch attribution analysis using Markov chains, Shapley values, and custom attribution models.
More from asgard-ai-platform/skills
All 207 skills in this repoAlgo Ecom Bm25
asgard-ai-platform/skills
Implement BM25 ranking function for e-commerce product search relevance scoring.
Algo Mfg Cpk
asgard-ai-platform/skills
Calculate Cpk process capability index to assess whether a process meets specification requirements.
Algo Price Elasticity
asgard-ai-platform/skills
Calculate price elasticity of demand to quantify how price changes affect sales volume.
Algo Rank Bayesian
asgard-ai-platform/skills
Apply Bayesian averaging to rank items by combining observed ratings with prior expectations.
Algo Rank Elo
asgard-ai-platform/skills
Implement Elo rating system to rank items or players from pairwise comparison outcomes.
Algo Rank Wilson
asgard-ai-platform/skills
Calculate Wilson Score confidence intervals for ranking items by positive proportion with sample size correction.
Related
Categories
Questions about Biz Customer Journey
What does Biz Customer Journey do?
Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages. Biz Customer Journey is an agent skill from asgard-ai-platform/skills. Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages.
When should I use Biz Customer Journey?
Biz Customer Journey fits situations like: the user needs to understand the customer experience end-to-end; identify drop-off points; optimize touchpoints; improve conversion — even if they say where are we losing customers.
How do I install Biz Customer Journey in Claude Code?
Run `npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a claude-code`. Or copy the skill folder (biz-customer-journey in asgard-ai-platform/skills) into .claude/skills/biz-customer-journey in your project. Claude Code loads it when a task matches its description.
How do I install Biz Customer Journey in Codex?
Run `npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a codex`. Or copy the skill folder (biz-customer-journey in asgard-ai-platform/skills) into .agents/skills/biz-customer-journey in your project. Codex loads it when a task matches its description.
Can I use Biz Customer Journey in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asgard-ai-platform/skills --skill biz-customer-journey -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/biz-customer-journey, .gemini/skills/biz-customer-journey, .github/skills/biz-customer-journey and .opencode/skills/biz-customer-journey in your project.
What does Biz Customer Journey need to run?
SKILL.md names no scripts, command-line tools or credentials: Biz Customer Journey is instructions for the agent only.
Does Biz Customer Journey access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Biz Customer Journey safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Biz Customer Journey use?
Biz Customer Journey is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Biz Customer Journey use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.
What are the alternatives to Biz Customer Journey?
Skills that share tags, products or a category with Biz Customer Journey: User Story Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), QA Critical UX (fastrepl/anarlog, 9.5k stars), Prd (juanandresgs/claude-ctrl, 193 stars) and Customer Journey Map Builder (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Biz Customer Journey?
asgard-ai-platform (a GitHub organization) maintains it in asgard-ai-platform/skills, which has 242 GitHub stars. The repository holds 207 skills in this directory. The repository was last updated on June 6, 2026.
Source: asgard-ai-platform/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.