visa-modelador

Generate domain.md, flows.md, business_model.md, architecture.md, and integrations.md from discovery evidence.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Adgmed2018/visa --skill visa-modelador
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visa-modelador
Source: https://github.com/Adgmed2018/visa/tree/main/agents/visa-modelador
Command: npx skills add https://github.com/Adgmed2018/visa --skill visa-modelador

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Synthesizes pains, opportunities, and evidence into an executable product domain model, guiding early product decisions and alignment across teams.

Core Features & Use Cases

  • Executable product model: outputs domain model, main flows, business model, and integration map as living artifacts to drive discovery and handoffs.
  • Decision surfacing: captures how to resolve critical design questions and decisions proactively.
  • Use Case: given research findings, generate domain.md, flows.md, and architecture.md to hand to architects and engineers.

Quick Start

Lay out the product domain from discovery data and produce domain.md, flows.md, architecture.md, and integrations.md ready for review.

Frequently Asked Questions about visa-modelador

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

FAQPage Schema
How do I translate discovery evidence into an executable product model?

To build an executable product model from discovery evidence, you synthesize pains, opportunities, and constraints into structured artifacts including domain.md, flows.md, and architecture.md. This approach translates raw findings into living documents that guide early design.

What artifacts are needed to map product domain flows and architecture for engineers?

Mapping product domain flows and architecture requires generating domain.md, flows.md, architecture.md, business_model.md, and integrations.md. These artifacts provide the structured traceability needed to inform design decisions and hand off discovery findings.

Can I generate a business model hypothesis from early-stage product discovery data?

Yes, you can generate a business model hypothesis from early-stage product discovery data. By synthesizing research findings and constraints, the process outputs business_model.md to capture and test critical business decisions.

Does this approach surface design decisions and integration requirements proactively?

This approach proactively surfaces design decisions by capturing how to resolve critical questions early. It also maps integration requirements through integrations.md, ensuring alignment across teams before implementation begins.

When do I need to create an executable product domain model during discovery?

You need to create an executable product domain model during early-stage product discovery when teams require structured domain models, flows, and architecture. It translates evidence into actionable artifacts to guide alignment and implementation.

How to hand off discovery findings to architects using structured domain models?

To hand off discovery findings to architects, you generate structured domain models and architecture documents. By transforming research evidence into domain.md and architecture.md, you provide engineers with clear, traceable design guidance.