workflow-designlisted

Models, proves, measures, and safely changes multi-step workflows — approval chains, review pipelines, intake/triage/fulfillment flows, ticketing, order processing, state machines with human gates. Use when designing states/gates/transitions or an audit trail, when a status field or event log is being added to a system, when tests guarding a workflow need auditing ("the suite is green but I don't trust it"), when someone asks where items get stuck, whether an approval step is worth keeping, who approved something, or why a queue is growing, or when a live workflow's definition must change with items still in flight. Also covers spreadsheet/paper approval processes, human review of AI or agent output, SLA/escalation design, and the workflow-engine-vs-hand-rolled decision. Stack-agnostic; ships four dependency-free tools (flow linter, guard red-proof runner, transition-log metrics, log-vs-model conformance).
ghorbanies/workflow-design · ★ 1 · AI & Automation · score 75

Install: claude install-skill ghorbanies/workflow-design

# Workflow design, proof, and dynamics A workflow is anything an item moves through: intake → review → approval → fulfillment, draft → edit → publish, ticket → triage → assignment → close. It has **stations** (where an item waits), **gates** (where a decision is made), and **transitions** (how it moves). ## Which phase am I in? Route by the situation, not by curiosity — read only the reference the task needs: - **Designing a flow, adding a status field, or reviewing a data model** → Phase 1. - **Auditing tests, a green suite that shipped a bug, "do these tests protect anything?"** → Phase 2. - **"Where do items get stuck?", "is this approval step worth it?", reading an event log** → Phase 3. - **The flow's definition is changing while items are in flight** → Phase 4 (and capture the Phase 3 baseline *first*). And four contexts that change *where* the rules land, not the rules — read alongside the phase you are in: - **No code at all** — the flow runs on spreadsheets, forms, or paper → [references/human-flows.md](references/human-flows.md) (the log is a sheet; the CSV bridge feeds `dynamics.py` unchanged). - **A human gate reviews AI/agent output** — drafts, classifications, proposed actions → [references/ai-gates.md](references/ai-gates.md) (the agent is an actor, never a decider; rubber-stamp detection; a prompt change is a flow change). - **Time promises** — SLAs, deadlines, reminders, escalation → [references/slas.md](references/slas.md) (an SLA needs an