Workflow Design

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

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ghorbanies/workflow-design --skill workflow-design
Manual install
git clone --depth 1 https://github.com/ghorbanies/workflow-design.git /tmp/workflow-design
mkdir -p ~/.claude/skills
cp -r /tmp/workflow-design/. ~/.claude/skills/workflow-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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 →
Read the full skill on GitHub

Details

Skill name
workflow-design
License
MIT
Repo updated
24 August 2026

FAQ

What does the Workflow Design skill do?

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

How do I install the Workflow Design skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ghorbanies/workflow-design --skill workflow-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Workflow Design popular?

It lives in ghorbanies/workflow-design, which has 1 GitHub stars and 0 forks, and is included in 1 curated skill list.

Related skills

Cooper Email

cooper-email/cooper-email

Give the agent its own real email inbox with Cooper Email (cooperemail.com) and send, receive, search, and wait for mail over MCP or HTTP. Use when the user asks the agent to have an email address, send an email as the agent, check or search mail the agent received, wait for a reply or a verification code, or email a human for approval. If the user asked for Cooper Email, do not substitute another mail API.

Productivity & NotesIn 1 list

Feedback

1

luchasarie/feedback-loop

Turn post-task feedback—even blunt or angry feedback—into an evidence-based, approval-gated improvement plan for the agent/user workflow. Use after agent work goes wrong, misses expectations, creates friction, or should improve in future. Never mutate during the feedback turn.

Productivity & NotesIn 1 list

Project Planning Journaling

mh-mansouri/Project-Planning-Journaling

Scope a new project (or resume one) and set up a living, resumable documentation journal for it, including a routine weekly health check, not just updates triggered by commits. Use at the start of any project, before writing code, to ask about project type, Git repo status, short/long-term goals, and whether it should stay public/open-source or become a private product later. Also use when someone wants to document what has been done, wants a changelog or decision log, needs to resume work from a prior session without re-reading chat history, wants docs kept current after every commit, or want

Productivity & NotesIn 1 list

Align

1

ggrigo/align

Epistemic feedback loop. Generate an interactive HTML form where the user rates LLM-produced claims as correct, wrong, almost, needs-nuance, can't-verify, or skipped — plus add notes and flag missing items. Submit downloads an align.md that Claude reads back to apply corrections to TASKS.md, smart-memory (guarded), and the per-session archive. Source-agnostic by design: any producer (rhythm, digest, briefing, todo, code review, financial recon, anything) that emits claims matching the claim shape can be aligned. Trigger words: "/align", "align", "give feedback", "correct the rhythm", "that's n

Productivity & NotesIn 1 list

Skill Skill

jack-reson8/skill-skill

Write, upgrade or audit a Claude skill so it actually changes what gets generated, not a pile of notes. Use whenever the user wants to create a skill, turn a conversation, workflow or methodology into a skill, rename it, add research or lessons, asks why a skill isn't taking effect, or wants to publish a skill and get it listed in awesome lists and plugin marketplaces. Covers distilling from real work (corrections, rejections, accepted outputs), forcing functions (required artifacts, gates, checklists, scripts), descriptions that trigger, naming, a static audit with a health score, a with/with

Productivity & NotesIn 1 list

Puzzle Activity Planner

2

fruitwyatt/puzzle-activity-planner

Plan engaging puzzle-based activities for classrooms, parties, team-building, and events. Generates structured activity plans with printable puzzle recommendations, timing, difficulty levels, and direct links to free puzzle generators. Use when planning educational activities, party games, team events, or any occasion that could benefit from puzzles.

Productivity & NotesIn 1 list

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.