metodologia-flow-mapping

Map domain boundaries and 8-12 end-to-end business flows with sequence diagrams.

Updated Mar 31, 2026

Search Tags:#ddd #domain-driven-design #risk-analysis #dependency-graph #flow-mapping #sequence-diagrams #integration-matrix

Ready to run

npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-flow-mapping

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metodologia-flow-mapping
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/discovery/flow-mapping
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-flow-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Flow Mapping provides a structured method to translate AS-IS system observations into a formal map of bounded contexts, domain taxonomies, end-to-end business flows, and the dependencies that tie them together, enabling better planning and risk analysis.

Core Features & Use Cases

Domain Taxonomy (DDD) with Domain Cards and context mapping.
8-12 end-to-end flows with trama specifications, sequence diagrams, and integration matrix.
Critical Failure Points and System Dependency Graphs for risk management.
Outputs suitable for executive briefings and technical reviews.

Quick Start

Run flow-mapping on the target codebase to produce a complete 8-12 flow map with domain taxonomy, sequence diagrams, trama specifications, and an integration matrix.

Frequently Asked Questions about metodologia-flow-mapping

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

FAQPage Schema

How do I map domain boundaries and end-to-end business flows for DDD architecture reviews?▼

Flow mapping identifies bounded contexts and captures 8-12 end-to-end business flows to enable reliable system understanding. It produces a DDD taxonomy, sequence diagrams, and an integration matrix suitable for architecture reviews and risk analysis.

What's the best way to document sequence diagrams and failure points for system integrations?▼

Documenting sequence diagrams and critical failure points involves mapping end-to-end business flows and their messages. Flow mapping generates trama specifications and dependency graphs to formalize integration points and support resilience analysis.

How does dependency graph generation work for domain-driven design risk analysis?▼

Dependency graph generation for DDD risk analysis works by translating AS-IS system observations into a formal map of bounded contexts. It identifies critical failure points across core domains to produce structured matrices for delivery planning.

Can I use flow mapping to create an integration matrix for multiple bounded contexts?▼

Yes, flow mapping applies to maps of bounded contexts, integrations, and dependencies across core domains. It outputs a structured integration matrix alongside domain cards and context mapping to satisfy traceability requirements.

When do I need trama specifications and domain taxonomy for delivery planning?▼

Trama specifications and domain taxonomy are needed when translating AS-IS system observations into formal maps for delivery planning. Flow mapping captures end-to-end flows with sequence diagrams and failure points to de-risk integrations.

What limitations should I consider when capturing end-to-end business flows across core domains?▼

Capturing end-to-end business flows requires observing AS-IS system states to accurately identify bounded contexts. Flow mapping focuses on 8-12 flows and produces dependency graphs, meaning undocumented or ad-hoc integrations outside core domains may be missed.