[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GHDFJGPZ5KC6DSF5X7S82":3,"skill-same:01M74GHDFJGPZ5KC6DSF5X7S82":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GHDFJGPZ5KC6DSF5X7S82","customer-journey",null,"Map one persona's path through one JTBD — stages, what they're doing\u002Fthinking\u002Ffeeling, touchpoints, pain; mark evidence vs assumption.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-research\u002Fskills\u002Fcustomer-journey\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: customer-journey\ndescription: Map one persona's path through one JTBD — stages, what they're doing\u002Fthinking\u002Ffeeling, touchpoints, pain; mark evidence vs assumption.\n---\n\n# customer-journey\n\n> One persona, one job-to-be-done, 5–7 stages. Multiple personas → multiple journeys; don't merge.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A team has a persona doc and wants to surface where in the user's flow they're losing.\n- Funnel analytics show drop-off but the team doesn't know why.\n\n## Inputs\n\n- The persona doc (required).\n- The job-to-be-done in JTBD form (\"When \u003Csituation>, I want to \u003Cmotivation>, so I can \u003Coutcome>.\").\n- Optional: existing funnel analytics.\n\n## Procedure\n\n1. Read [`Customer-journey.md`](..\u002F..\u002Ftemplates\u002FCustomer-journey.md).\n2. **Slug** from the JTBD's outcome clause: a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n3. Draft `docs\u002Fresearch\u002Fjourneys\u002F\u003Cslug>.md`:\n   - **JTBD** — verbatim in the doc.\n   - **Stages** — 5–7. User-perspective, not product features. Trigger → Search → Evaluate → Onboard → First success → Habit → Tell others is a good default.\n   - **Per stage** — what they're doing, thinking\u002Ffeeling, touchpoints, pain.\n   - **Peak pain moments** — the 1–2 highest-drop-off stages. These are the leverage points.\n   - **Evidence vs assumption** — mark every stage `✓ Evidence` (quote-supported) or `? Assumption` (guess).\n   - **Improvements** — top 3 changes sized by impact, with the metric each would move.\n\n## Quality bar\n\n- Stages are user-perspective (\"evaluating options\"), not product-perspective (\"uses comparison page\").\n- Every stage marked Evidence or Assumption. Assumption-heavy journeys are flagged for research before action.\n- Peak pain moments named explicitly.\n- One persona per journey. Multi-persona journeys are merged guesses.\n\n## Output\n\n- File: `docs\u002Fresearch\u002Fjourneys\u002F\u003Cslug>.md`.\n- Summary listing the 2 peak pain moments + the top improvement.\n\n## Anti-patterns to avoid\n\n- Generic \"AAARRR\" funnel re-labeled as a journey. The stages must reflect this specific JTBD.\n- Stages full of `? Assumption` shipped as if they were research.\n- \"Delight\" stage added as a vanity step. If there's no evidence of delight, don't add it.\n- Improvements sized by \"ease\" or \"what we can ship next sprint\" instead of impact.\n","# customer-journey\n\n> One persona, one job-to-be-done, 5–7 stages. Multiple personas → multiple journeys; don't merge.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- A team has a persona doc and wants to surface where in the user's flow they're losing.\n- Funnel analytics show drop-off but the team doesn't know why.\n\n## Inputs\n\n- The persona doc (required).\n- The job-to-be-done in JTBD form (\"When \u003Csituation>, I want to \u003Cmotivation>, so I can \u003Coutcome>.\").\n- Optional: existing funnel analytics.\n\n## Procedure\n\n1. Read [`Customer-journey.md`](..\u002F..\u002Ftemplates\u002FCustomer-journey.md).\n2. **Slug** from the JTBD's outcome clause: a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n3. Draft `docs\u002Fresearch\u002Fjourneys\u002F\u003Cslug>.md`:\n   - **JTBD** — verbatim in the doc.\n   - **Stages** — 5–7. User-perspective, not product features. Trigger → Search → Evaluate → Onboard → First success → Habit → Tell others is a good default.\n   - **Per stage** — what they're doing, thinking\u002Ffeeling, touchpoints, pain.\n   - **Peak pain moments** — the 1–2 highest-drop-off stages. These are the leverage points.\n   - **Evidence vs assumption** — mark every stage `✓ Evidence` (quote-supported) or `? Assumption` (guess).\n   - **Improvements** — top 3 changes sized by impact, with the metric each would move.\n\n## Quality bar\n\n- Stages are user-perspective (\"evaluating options\"), not product-perspective (\"uses comparison page\").\n- Every stage marked Evidence or Assumption. Assumption-heavy journeys are flagged for research before action.\n- Peak pain moments named explicitly.\n- One persona per journey. Multi-persona journeys are merged guesses.\n\n## Output\n\n- File: `docs\u002Fresearch\u002Fjourneys\u002F\u003Cslug>.md`.\n- Summary listing the 2 peak pain moments + the top improvement.\n\n## Anti-patterns to avoid\n\n- Generic \"AAARRR\" funnel re-labeled as a journey. The stages must reflect this specific JTBD.\n- Stages full of `? Assumption` shipped as if they were research.\n- \"Delight\" stage added as a vanity step. If there's no evidence of delight, don't add it.\n- Improvements sized by \"ease\" or \"what we can ship next sprint\" instead of impact.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-research\u002Fskills\u002Fcustomer-journey","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill customer-journey",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill customer-journey",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill customer-journey","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-research\u002Fskills\u002Fcustomer-journey\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]