메뉴
End-to-end customer journey mapping engine with gated progression model that designs every touchpoint from awareness through advocacy. Use when: customer journey, buyer journey, journey map, touchpoints, conversion funnel, buying process, customer experience mapping.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | journey-architect |
| description | End-to-end customer journey mapping engine with gated progression model that designs every touchpoint from awareness through advocacy. Use when: customer journey, buyer journey, journey map, touchpoints, conversion funnel, buying process, customer experience mapping. |
Design the complete customer journey with measurable gates. Maps every touchpoint from first awareness through purchase, activation, and advocacy with friction scoring at each stage.
Critical inputs (ask if not provided):
Nice-to-have:
Each gate represents a cognitive/behavioral milestone customers must pass through:
| Gate | Name | Customer State | Key Question They Ask |
|---|---|---|---|
| G1 | Awakening | Recognizes they have a problem | "Is this actually a problem worth solving?" |
| G2 | Exploration | Begins researching solutions | "What options exist to solve this?" |
| G3 | Consideration | Builds a shortlist | "Which 2-3 solutions should I evaluate seriously?" |
| G4 | Conviction | Commits to a solution | "Can I justify this purchase internally?" |
| G5 | Activation | Starts using the product | "How do I get value from this quickly?" |
| G6 | Integration | Product becomes embedded in workflow | "How does this fit into everything else I do?" |
| G7 | Amplification | Becomes an advocate | "Who else needs to know about this?" |
For EACH gate, document:
Entry Trigger: What event causes the customer to enter this gate?
Information Needs: What content/evidence do they need?
Touchpoints: Where do they interact?
Friction Points: What slows them down or causes abandonment?
Exit Criteria: What must be true for them to advance?
Conversion Benchmark: Target percentage that pass through
Map each persona through the 7 gates separately:
For every friction point identified, score:
| Factor | Scale | Description |
|---|---|---|
| Severity | 1-5 | How badly does it block progression? |
| Frequency | 1-5 | What % of customers hit this? |
| Fix Difficulty | 1-5 | How hard to resolve? (inverse for priority) |
Priority Score = (Severity x Frequency) / Fix Difficulty
Sort descending. Top 10 friction points become the action list.
Save to outputs/journey-map-[product]-[YYYY-MM-DD].md
battle-scanner to understand how competitors perform at each gatedemand-engine (G1-G2 needs become demand gen strategy), enablement-forge (G3-G4 needs become sales assets), growth-loop (G5-G7 design becomes retention strategy)market-analyzer (segment data shapes persona paths)Customer analytics framework - cohort retention, lifecycle funnels, engagement scoring, segmentation, and behavioral diagnostics for product and CS teams. Use when: customer analytics, cohort analysis, retention curve, engagement score, customer segmentation, behavioral analysis, lifecycle funnel, RFM, activation diagnostics, usage analysis.
Account-Based Marketing playbook builder - tiered account list (1:1, 1:few, 1:many), buying-group mapping, coordinated multi-channel plays per account, and pipeline acceleration plays for in-cycle accounts. Use when: ABM playbook, account-based marketing, target account list, tiered accounts, 1:1 marketing, buying group, named-account strategy, ABM plays, pipeline acceleration, in-cycle account acceleration.
On-demand sales battlecards for live competitive deals - positioning matrix, top objections with responses, trap questions, proof points, and a "do not say" list. Use when: competitor surfaced in deal, sales battlecard, competitive enablement, deal-specific battlecard, objection handling, competitive trap questions, why we win against, why we lose to, displacement playbook.
Customer advocacy program design - advocate identification, reference orchestration, case study pipeline, community amplification, and influence-to-revenue attribution. Use when: customer advocacy, customer reference program, case study program, advocate identification, customer marketing, peer review acceleration, G2 / Gartner Peer Insights, customer-led growth, reference architecture.
Customer Success operating system - segmented coverage model, health scoring, risk playbooks, value reviews, and expansion motions tied to net revenue retention. Use when: customer success strategy, CS operating model, health score, risk playbook, EBR / QBR design, churn prevention, net retention, NRR, GRR, success plan, value realization, customer journey post-sale.
Lead nurture orchestration - multi-track nurture design by intent stage, scoring, behavioral triggers, MQL→SQL handoff, and revival of cold leads. Use when: lead nurture, drip campaign, nurture track, lead scoring, MQL to SQL, lifecycle marketing, nurture sequence, behavioral trigger, lead revival, MQL handoff.