Systems and engineering recipe · Data flow diagram
Which events move through which topics, processors, groups, and failure paths?
Draw it as a data-flow diagram with the MosoFin-diagram "Event-stream topology" recipe. A stream map of producers, topics, ordered processors, consumer groups, state, replay, and DLQ. Your coding agent returns one validated, self-contained HTML file.
When to use this diagram
Kafka/event-platform design, stream processing reviews, ownership, replay, and failure handling.
Pick another recipe when topic names, consumer groups, and delivery semantics are not known—use a generic workflow instead.
What the diagram must include
- Producers and event names
- Topics and ordering
- Processors and consumer groups
- State, replay, and DLQ
Copy-ready prompt
Paste this into your coding agent with MosoFin-diagram installed. Recipe ID: event-stream.
Use Mosofin dataflow mode to draw this event-stream topology. Name producers, events, topics, ordered processors, consumer groups, state stores, replay paths, and the DLQ. Show ownership and delivery semantics only when supported by evidence.How to make it
- Install the skill. Add MosoFin-diagram to your coding agent. For Claude Code: npx -y skills add MosoFin/mosofin-diagram --skill mosofin --agent claude-code --global --copy --yes
- Describe the business once. Answer a short interview: what the business does, which entities are in scope, and which system of record owns each domain.
- Ask this question. Paste the Event-stream topology prompt from this page. The agent writes the diagram spec, validates it, and repairs anything the validator names.
- Open and share the diagram. Open the self-contained HTML file in any browser, walk the guided views, and forward it or export an image.
Verified example
Northline Coffee — Stripe Payout Reconciliation to Chase 1002 (2026-07) is a real data flow diagram delivered by the skill and checked by its validator.
Questions about this recipe
Which diagram type answers “Which events move through which topics, processors, groups, and failure paths?”
A data flow diagram. Revenue walks, payout reconciliations, cash runway and data lineage: where a number comes from. The Event-stream topology recipe sets it up for this question.
When should I use a different recipe?
Pick another recipe when topic names, consumer groups, and delivery semantics are not known—use a generic workflow instead.
Does MosoFin-diagram connect to my systems or invent numbers?
No. It draws only what you state in the business brief or the conversation. It never calls QuickBooks, Stripe, Shopify, an ERP or a bank, and an amount you did not supply never appears.