Systems and engineering recipe · Lifecycle diagram
What state is a release in, and what can happen next?
Draw it as a lifecycle diagram with the MosoFin-diagram "Deployment lifecycle" recipe. A deployment state model covering queued, building, verifying, approval, promotion, rollback, and terminal outcomes. Your coding agent returns one validated, self-contained HTML file.
When to use this diagram
Release controllers, GitOps reconciliation, environment promotion, or deployment status APIs.
Pick another recipe when the question is the human/CI sequence of delivery actions rather than the deployment object state.
What the diagram must include
- Queued and running states
- Verification and approval
- Promotion and rollback
- Success, failure, cancellation
Copy-ready prompt
Paste this into your coding agent with MosoFin-diagram installed. Recipe ID: deployment-lifecycle.
Use Mosofin lifecycle mode to model the deployment object. Show queued, building, verifying, waiting for approval, promoting, rolling back, and every terminal outcome. Label the events and guards that permit each transition.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 Deployment lifecycle 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 — Refund and Chargeback Lifecycle (2026-07) is a real lifecycle diagram delivered by the skill and checked by its validator.
Questions about this recipe
Which diagram type answers “What state is a release in, and what can happen next?”
A lifecycle diagram. The states one object moves through: refunds, disputes, invoices, subscriptions. The Deployment lifecycle recipe sets it up for this question.
When should I use a different recipe?
Pick another recipe when the question is the human/CI sequence of delivery actions rather than the deployment object state.
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.