flow-architecture

Integrate Wardley Mapping, DDD, and Team Topologies to design organizational flow.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Gami19/rd-strands-agents --skill flow-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-architecture
Source: https://github.com/Gami19/rd-strands-agents/tree/main/strands-py/backend/agent/skills/pr/flow-architecture
Command: npx skills add https://github.com/Gami19/rd-strands-agents --skill flow-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to align business strategy, software architecture, and team organization by applying Wardley Mapping, Domain-Driven Design, and Team Topologies to enable faster, more reliable change flows.

Core Features & Use Cases

  • Integrates Wardley Mapping, DDD, and Team Topologies to produce a unified Architecture for Flow Canvas.
  • Supports as-is and to-be analyses, subdomain classification, bounded-context design, and team-constellation planning.
  • Use case: a legacy monolith modernization project can be planned with value streams, evolution stages, and transition roadmaps.

Quick Start

Create Architecture for Flow Canvas by mapping current teams, flow, and value chain, then design a future state with BCs and team topology.

Frequently Asked Questions about flow-architecture

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

FAQPage Schema
How do I align Wardley Mapping, DDD, and Team Topologies to optimize organizational flow?

Aligning Wardley Mapping, DDD, and Team Topologies optimizes organizational flow by integrating value chain analysis, bounded-context design, and team interaction planning into a unified Architecture for Flow Canvas.

What is the best way to design team topologies and bounded contexts from a Wardley Map?

Designing team topologies and bounded contexts from a Wardley Map involves mapping current value chains, classifying subdomains, and planning team constellations to transition from as-is monolithic states to to-be flow architectures.

Can I use this approach to plan a legacy monolith modernization roadmap?

You can plan legacy monolith modernization roadmaps by applying this approach to map existing value streams, classify evolution stages, design bounded contexts, and define transition states for future team topologies.

How does the Architecture for Flow Canvas support as-is and to-be organizational analysis?

The Architecture for Flow Canvas supports as-is and to-be organizational analysis by mapping current teams and flow, then designing future states with bounded contexts and team constellations for reliable change delivery.

Do I need prior experience with Domain-Driven Design to map value chains and team interactions?

Prior Domain-Driven Design experience is beneficial for mapping value chains and team interactions, as the process requires subdomain classification and bounded-context design to effectively structure future team topologies.

When should I not use an integrated flow architecture approach for team organization?

You should avoid using an integrated flow architecture approach when your organization cannot support the prerequisite strategic mapping of value chains, or when team boundaries do not align with distinct bounded contexts.