phase-gate

Coordinate pre-phase and post-phase agent selection gates with human approval.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/turbobeest/dev-system --skill phase-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-gate
Source: https://github.com/turbobeest/dev-system/tree/main/skills/phase-gate
Command: npx skills add https://github.com/turbobeest/dev-system --skill phase-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and scripts (resource) and references (resource) components.

What problem does it solve?

Manages pre-phase and post-phase agent selection gates. Coordinates visual phase headers and human gates to ensure the right agents are engaged at each boundary.

Core Features & Use Cases

  • Gate orchestration: Pre-phase and post-phase gates with recommended defaults.
  • Human approval: Visual prompts for human confirmation before proceeding.
  • Agent locking: Lock selections and emit transition signals to the next phase.

Quick Start

On phase transitions, use [ACTIVATE:PHASE_GATE_V1] to display pre/post gates and confirm the next set of agents.

Frequently Asked Questions about phase-gate

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

FAQPage Schema
How do I coordinate agent selection across phase boundaries in multi-phase pipelines?

Phase-gate coordinates pre-phase and post-phase agent selection at each transition, displaying visual headers and collecting human approval before locking executor and auditor choices. Activation via [ACTIVATE:PHASE_GATE_V1] manages the boundary handoff and emits signals for downstream orchestration.

What's the best way to ensure the right executors and auditors are engaged at each workflow phase?

Phase-gate provides pre-phase gates with recommended defaults, human confirmation prompts, and agent locking to align executors with auditors. It interfaces with .claude/phase-agents.json and ASCII headers to surface phase-state changes and selected agents before proceeding.

Can I automate agent handoff with human approval gates in AI agent workflows?

Yes. Phase-gate automates the selection process with context-aware defaults, then surfaces visual gates requiring explicit human confirmation at each phase transition before agents are locked and transition signals are emitted.

How do phase gates differ from manual agent assignment in multi-phase AI workflows?

Phase gates introduce structured boundaries with recommended defaults, visual confirmation prompts, and atomic agent locking, ensuring coordinated executor-auditor pairs and explicit checkpoints instead of ad-hoc assignment changes mid-workflow.

What happens when I activate phase-gate at a transition point?

Phase-gate displays pre-phase and post-phase gates with recommended agents, collects human approval, locks the selected executors and auditors, updates phase-state in .claude/phase-agents.json, and emits downstream signals for the next phase.

Do I need existing agent configuration to use phase gates?

Phase-gate works with .claude/phase-agents.json and builds on ASCII UI headers; it augments defaults contextually, so you can start with minimal configuration and refine agent selections at each boundary.