Agent skill · design visual · erichowens
human-gate-designer
Designs human-in-the-loop review points for DAG workflows. Determines what to present to the human, how to collect feedback, and how to route approve/reject/modify decisions back into the DAG.
Why this skill is useful
Provides specific design patterns and decision trees for integrating human review points into DAG workflows that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-07-14. 180 stars on the source repository.
What this skill does
Human Gate Designer Designs human-in-the-loop review points in DAG workflows: what to present, how to collect feedback, how to route decisions back into the DAG. --- When to Use ✅ Use for: Deciding WHERE in a DAG to place human gates Designing WHAT the human sees at each gate Defining HOW feedback routes back (approve/reject/modify) Balancing automation speed with human oversight ❌ NOT for: Runtime execution of human gates (use dag-runtime + Temporal signals) General UI/UX design (use design skills) Chatbot conversation flow (different pattern) --- Gate Placement Decision Tree Where to Place Gates Situation Gate Position Why ----------- ------------- ----- Irreversible action (deploy, send email, submit) Before the action Can't undo User-facing deliverable (report, website, PR) After generation, before delivery Quality check High cost remaining (>$0.50) Before expensive phase Budget confirmation Low confidence output (<0.7) After the uncertain node Expert judgment needed Ambiguous task decomposition After planning, before execution Validate the plan First run of a new template DAG After each phase Build trust gradually --- Gate Presentation Design What the Human Sees Presentation Principles 1. Show context, not just output: The human needs to understand what the DAG has done so far, not just the current node's result. 2. Highlight decisions: Bold or annotate the choices the agent made. These are what the human is actually reviewing. 3. Show confidence: If the agent was uncertain, say so. Low-confidence outputs need more scrutiny. 4. Show cost: The human should know what they've spent and what's remaining. 5. Make "Modify" easy: A text input for feedback that gets injected into the retry prompt. --- Feedback Routing Feedback Injection When the human selects "Modify," their text becomes part of the re-execution prompt: --- Anti-Patterns Gate After Every Node Wrong: Requiring human approval after every single node. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills erichowens/human-gate-designer