visa-estrategista

Analyze domain journeys to extract pains, gains, frictions, and product opportunities.

Updated May 4, 2026

Search Tags:#analyze #evidence-based #journeys #product-strategy #frictions #user-pains #visa-sdd

Ready to run

npx skills add https://github.com/Adgmed2018/visa --skill visa-estrategista

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: visa-estrategista
Source: https://github.com/Adgmed2018/visa/tree/main/agents/visa-estrategista
Command: npx skills add https://github.com/Adgmed2018/visa --skill visa-estrategista

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deep domain analysis that walks journey-by-journey to surface specific pains, expected gains, frictions, critical moments, and product opportunities, acting as the forward-facing mirror to Reversa Archaeologist.

Core Features & Use Cases

Deep journey analysis per Ethnographer output to surface explicit pains, implicit frictions, and critical moments.
Generates functional, emotional, and social gains for each pain, enabling targeted product decisions.
Outputs structured artifacts (journey.md, pains-.md, frictions-.md, journeys.json) to feed downstream modeling and decision gates.

Quick Start

Analyze the journeys listed in .visa/plan.md and produce the corresponding pains, frictions, gains, and opportunities for each journey.

Frequently Asked Questions about visa-estrategista

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

FAQPage Schema

How do I analyze customer journeys to extract user pains and frictions?▼

Analyzing domain journeys involves walking through each journey to extract specific pains, gains, frictions, and product opportunities. It generates functional, emotional, and social gains for each pain, enabling evidence-based strategic guidance for product decisions.

What is evidence-based product strategy and how does it use journey artifacts?▼

Evidence-based product strategy uses structured journey artifacts like journey markdown files and a consolidated journeys.json to guide decisions. These deterministic, versioned outputs capture pains, frictions, and opportunities to feed downstream modeling and decision gates.

How do I generate structured outputs from discovery work for downstream modeling?▼

To generate structured outputs from discovery work, you analyze journeys listed in your plan to produce end-to-end artifacts. This yields journey markdown files, pains and frictions documents, and a consolidated journeys.json containing deterministic, versioned results for downstream decision gates.

Can I use journey analysis outputs for product opportunities if I only have a plan file?▼

Yes, you can analyze journeys identified in a plan file to extract product opportunities. By reading the journeys listed in your context, the analysis produces structured artifacts detailing pains, gains, and frictions without requiring additional dependencies.

What is the best way to identify critical moments and implicit frictions in user journeys?▼

The best way to identify critical moments and implicit frictions is through deep journey-by-journey analysis. This approach surfaces specific pains and expected gains, acting as a forward-facing mirror to archaeological discovery work for targeted product opportunities.