control-plane-what-next

Select the next eligible Forge Pipeline item after a task completes.

Updated Mar 30, 2026

Search Tags:#model-routing #control-plane #safety-gates #forge-pipeline #priority-scoring #auto-dispatch

Ready to run

npx skills add https://github.com/harkers/forge-email-server --skill control-plane-what-next

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: control-plane-what-next
Source: https://github.com/harkers/forge-email-server/tree/main/skills/control-plane-what-next
Command: npx skills add https://github.com/harkers/forge-email-server --skill control-plane-what-next

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically determine the next highest-priority, eligible Forge Pipeline item after a control-plane task completes, applying policy checks, safety gates, and approval windows to decide whether to dispatch or hold.

Core Features & Use Cases

Deterministic priority scoring and tie-break rules to identify the next work item from Forge Pipeline.
Safety gates, approval-window checks, and token-budget enforcement to govern auto-dispatch and operator intervention.
Model routing, per-pool capacities, and state persistence for reliable, auditable dispatch decisions.

Quick Start

Dispatch the highest-priority eligible Forge Pipeline item after a task completes.

Frequently Asked Questions about control-plane-what-next

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

FAQPage Schema

How do I automate next-item dispatch from a Forge Pipeline after a task completes?▼

Automate next-item dispatch by applying deterministic priority scoring and tie-break rules to select the highest-priority eligible Forge Pipeline item, then validating safety gates before releasing it for execution.

What are safety gates in a deterministic pipeline auto-dispatch process?▼

Safety gates in pipeline auto-dispatch are policy checks and approval-window validations that strictly govern whether a selected work item is dispatched immediately or held for operator intervention.

How does model routing interact with per-pool capacities during pipeline dispatch?▼

Model routing evaluates per-pool capacities during pipeline dispatch to ensure the selected work item is assigned to an available resource pool, enforcing token budgets and maintaining auditable state persistence.

Can I enforce token budgets and approval windows simultaneously for control-plane tasks?▼

You can enforce token budgets and approval windows simultaneously for control-plane tasks, applying both constraints as safety gates to determine whether the dispatcher auto-releases or holds the next pipeline item.

What is the best way to handle tie-breaks when multiple Forge Pipeline items have the same priority score?▼

Handle priority score tie-breaks by applying deterministic tie-break rules that evaluate secondary criteria, ensuring a single, auditable next-item selection for control-plane dispatch without ambiguity.

Why does the dispatcher hold a high-priority Forge Pipeline item instead of auto-dispatching it?▼

The dispatcher holds a high-priority Forge Pipeline item when safety gates, approval-window checks, or token-budget enforcement fail validation, triggering operator-facing summaries for governance and manual recovery.