customer-experience

Frame customer problems and capture CE Gate evidence for design intent.

3|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill customer-experience-grimblaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-experience
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/customer-experience
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill customer-experience-grimblaz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reusable approach to framing customer language for issues, enabling consistent CE evidence collection and alignment with design intent across upstream and downstream work.

Core Features & Use Cases

  • Frames customer problems in customer language and captures CE Gate evidence to guide design decisions.
  • Enables drafting 2-4 customer-perspective scenarios with intent and functional checks, plus mapping to surface gates.
  • Provides a reusable reference for upstream framing and downstream verification, ensuring design intent is verifiable through evidence.

Quick Start

Describe the customer problem in customer language and capture CE evidence using the approved design intent reference.

Frequently Asked Questions about customer-experience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I frame customer problems to align with design intent?

Mapping customer journeys involves drafting 2-4 customer-perspective scenarios with intent and functional checks, then mapping them to surface gates. This structured approach ensures design intent remains verifiable through captured evidence.

What is CE Gate evidence and when do I need it for issue scoping?

Capturing CE Gate evidence requires describing the customer problem in customer language and applying approved design intent references. This reusable approach provides structured templates for consistent evidence collection across teams.

Can I use this customer experience methodology for both upstream and downstream work?

This approach distinguishes itself by providing reusable gate guidance, clear design intent references, and structured evidence templates. Unlike basic framing, it satisfies disciplined methodology requirements across upstream and downstream verification processes.

How do I create intent scenarios with functional checks for customer journeys?

Creating intent scenarios involves drafting 2-4 customer-perspective scenarios that include both intent and functional checks. These scenarios map directly to surface gates, providing verifiable design intent evidence for customer journey work.