gate

Coordinate human decision gates to pause and escalate high-stakes choices.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ether-moon/agent-atelier --skill gate-ether-moon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate
Source: https://github.com/ether-moon/agent-atelier/tree/main/plugins/agent-atelier/skills/gate
Command: npx skills add https://github.com/ether-moon/agent-atelier --skill gate-ether-moon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Human gates are the system's mechanism for pausing when a decision is too consequential for the agent team to make alone. They exist because some decisions — breaking API changes, auth flow modifications, data model pivots — are irreversible or affect too many people to risk getting wrong.

Core Features & Use Cases

  • Open gates to solicit human input for decisions with high irreversibility or broad impact.
  • List, view, and resolve gates, track statuses, and surface pending decisions to stakeholders.
  • Atomic multi-file state transitions via the state-commit workflow to maintain consistency across HDRs, work items, and loop state.

Quick Start

Open a gate for a pending decision by providing a question, justification, and options, then let the orchestrator manage open gates.

Frequently Asked Questions about gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pause an automated workflow for human approval on high-stakes decisions?

To pause an automated workflow for human approval, you can open a human decision gate by providing a question, justification, and options. The orchestrator then manages the open gate and surfaces the pending decision to stakeholders.

When should I use human decision gates in my workflow orchestration?

You should use human decision gates when choices are too consequential for the agent team to make alone, such as breaking API changes, auth flow modifications, or data model pivots. They exist because some decisions are irreversible or affect too many people.

How do I track and resolve pending decisions across my orchestration workflow?

To track and resolve pending decisions, you can list, view, and resolve gates while monitoring their statuses. The system coordinates escalations and user responses, and enforces atomic multi-file state transitions to maintain consistency across work items and loop state.

Does the state-commit workflow support recovery after an orchestration session restart?

Yes, the state-commit workflow supports recovery after session restarts. It applies during escalations, pending decision viewing, and user responses, ensuring atomic multi-file state transitions across HDRs, work-items, loop-state, and index updates.

What is the best way to maintain state consistency across work items during a human escalation?

The best way to maintain state consistency during a human escalation is to enforce atomic multi-file state transitions via the state-commit workflow. This ensures consistency across HDRs, work items, loop state, and index updates when resolving gates.