What problem does it solve? Business analysts and developers often need consistent, traceable diagrams (sequence, ERD, BPMN, state, use case) tied to requirement IDs, but producing them ad hoc leads to inconsistent formats and lost traceability. This Skill standardizes diagram production into a single MODEL.md artifact per session. ## Core Features & Use Cases - Eleven diagram modes: sequence, activity, activity-swimlane, BPMN, state, ERD, use case, D2 ERD, D2 activity, D2 architecture, and dbdiagram, each with a default format. - Multiple output formats: Mermaid, PlantUML, D2, and DBML source, with optional .d2/.dbml sidecar files for external renderers like the D2 CLI or dbdiagram.io. - Traceability and honesty guardrails: diagrams link to FR/US/AC IDs via trace_refs, and the contract forbids inventing actors or claiming Camunda XML or live D2 rendering without evidence. - Use Case: Given a set of functional requirements for a checkout flow, produce a Mermaid sequence diagram in MODEL.md with actors, trace references to FR IDs, open questions, and handoff notes. ## Quick Start Ask the agent to use biz-model with diagram=sequence to model the checkout flow and write the result into MODEL.md in the active session.