business-workflows

Document cross-service business workflows by generating end-to-end documentation and a Mermaid sequence diagram that captures domain boundaries, cross-service interactions, and governance rules across multiple services.

Mapping domain entities to services requires generating a service-to-domain mapping section that defines bounded context ownership, cross-context data exchange, and business relationships without technical field details.

Visualize circuit breaker fallback paths by generating a Mermaid business workflow sequence diagram that illustrates the end-to-end process, explicitly including alternate and fallback paths for resilience.

You can document cross-service data flows by generating a dedicated section that describes aggregation patterns, data ownership, and significant entry points like APIs, scheduled tasks, and events.

Yes, the generated business workflow documentation supports output directly to the .github/modernize/assessment/engines/facts/business-workflows.md file path, including guidance for future expansions.

You need workflow analysis documentation when applying this to projects with multiple services to capture domain boundaries, primary workflows, cross-service data flows, and business rules for clear governance and traceability.