dynamic-flow-architecture

Document cross-container runtime flows by applying standardized templates in .specs/flows and referencing the root AGENTS.md for scope. Generate C4 dynamic diagrams to map use-case sequences and ensure flow traceability across services.

A C4 dynamic diagram visualizes runtime interactions and execution sequences across containers. You need it to communicate cross-service flows clearly and ensure alignment between system goals and executed runtime behaviors in complex architectures.

Map use cases to runtime flow diagrams by creating a primary flow document named after your use case. Fill in the cross-container steps and generate corresponding C4 dynamic diagrams to govern flow traceability and alignment.

To start generating cross-container flow documentation, you need YAML frontmatter in SKILL.md defining the name and description. You then reference .specs/flows templates and AGENTS.md to structure your runtime sequences.

Yes, flow governance and traceability are supported through use-case mapping and standardized cross-container flow documentation. This ensures alignment between system goals and executed runtime interactions across services.

Without optional scripts, references, and assets, you are limited to basic guided documentation and C4 dynamic diagram templates. Extended guidance for complex architecture scenarios requires referencing these additional assets.