orchestrator-user-gates

Enforce user-input gates at P1, P2, P4, and P5 orchestration checkpoints.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-user-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-user-gates
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/orchestrator-user-gates
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-user-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This gating skill ensures that critical orchestration checkpoints require explicit user input, preventing premature subtask dispatch and enabling governance over AI-agent workflows.

Core Features & Use Cases

  • Pause for user input at P1, P2, P4, and P5 checkpoints to validate plans, boundary decisions, task completion, and retrospective outcomes.
  • Integrates with AskUserQuestion to present decision menus and record approvals, revisions, and notes for audit trails.
  • Provides lifecycle safeguards including classification-based routing, loop limits, and state consistency checks to maintain governance across multi-agent tasks.

Quick Start

Trigger the orchestrator to pause at the next checkpoint and present the AskUserQuestion menu to collect approval or revision input.

Frequently Asked Questions about orchestrator-user-gates

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

FAQPage Schema
How do I enforce user approval checkpoints in a multi-agent AI workflow?

User approval checkpoints in a multi-agent AI workflow are enforced by gating orchestration phases to require explicit human input before subtask dispatch. This prevents premature execution and ensures governance over complex delivery pipelines.

What are user-input gates in AI agent orchestration?

User-input gates in AI agent orchestration are mandatory pause points that require human review or approval before proceeding. They validate plans, boundary decisions, task completion, and retrospective outcomes during complex delivery phases.

How do I prevent premature subtask dispatch in multi-agent pipelines?

Premature subtask dispatch in multi-agent pipelines is prevented by applying lifecycle safeguards like classification-based routing and loop limits. These checks maintain state consistency and ensure governance across tasks.

Can I integrate user decision menus with AskUserQuestion for workflow governance?

Yes, workflow governance integrates with AskUserQuestion to present decision menus at checkpoints. This records approvals, revisions, and notes, creating an audit trail for boundary decisions and retrospective outcomes.

When do I need human-in-the-loop gating for AI agent delivery phases?

Human-in-the-loop gating for AI agent delivery phases is needed at phases P1, P2, P4, and P5. These checkpoints validate plans, boundary decisions, task completion, and retrospective outcomes to maintain governance.

What lifecycle safeguards are needed for governance across multi-agent tasks?

Lifecycle safeguards for governance across multi-agent tasks include classification-based routing, loop limits, and state consistency checks. These mechanisms prevent uncontrolled execution and ensure explicit user input at critical checkpoints.