agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/customer-journey-map/SKILL.md

customer-journey-map

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to create, map, analyze, improve, or visualize a customer journey, user journey, service journey, onboarding journey, buying journey, support journey, adoption journey, or end-to-end customer experience. Use for journey maps, stages, touchpoints, user actions, emotions, questions, pain points, drop-off points, friction, time to value, aha moment, moments of truth, churn triggers, retention opportunities, experience gaps, onboarding improvements, and prioritized journey improvements. Use for prompts like map the customer experience, where do users drop off, improve onboarding, identify friction points, map touchpoints, visualize the user journey, find pain points, what is the aha moment, why are users confused, or prioritize experience fixes. Do not use for GTM launch channels, customer-facing help articles, API docs, product requirements, broad product strategy, stakeholder influence mapping, or pure support-ticket response writing. If the primary task is launch channels, acquisition, messaging, or market-entry execution, use gtm-strategy. If the primary task is customer-facing support documentation, troubleshooting, setup, or API docs, use support-docs. If the primary task is PRD, feature requirements, or MVP scope, use create-prd. If the primary task is product direction, segments, trade-offs, or defensibility, use product-strategy. If the primary task is stakeholder alignment, approvals, or communication planning, use stakeholder-map.

19 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-okrs, outcome-roadmap and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • skytiger6724Skill

    outcome-roadmap

    Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

    Also in 5 projects that use this

  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 4 projects that use this

  • 45ckSkill

    porters-five-forces

    Also in 6 projects that use this

  • About-IntelligenceSkill

    value-proposition

    Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives.

    Also in 6 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 5 projects that use this

  • +6 more from skytiger6724

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free