beo-executing

Execute per-worker task loops with dispatch verification and phase progression.

Updated Jun 2, 2026

Search Tags:#automation #workflow #planning #orchestrator #quality-control #execute #task-beads

Ready to run

npx skills add https://github.com/minhtri2710/skills --skill beo-executing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beo-executing
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/executing
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-executing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill defines and coordinates the per-worker execution loop required to implement a single task at a time. It handles prompting a worker, dispatching the work, verifying outcomes, and looping back for the next task, ensuring disciplined progress from plan to completion.

Core Features & Use Cases

Executes one task at a time in a controlled loop: plan, dispatch, verify, report, and repeat until closed.
Supports both worker mode (direct execution) and standalone mode (dispatching subagents for multiple tasks) with consistent phase transitions.
Provides governance and guardrails for task readiness, dependencies, and reporting to downstream beads.

Quick Start

Run the per-worker execution loop on the next open task bead.

Frequently Asked Questions about beo-executing

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

FAQPage Schema

How do I automate task execution loops for dispatching workers and verifying results?▼

Automating task execution loops involves prompting a worker, dispatching work, verifying outcomes, and repeating until all tasks close. This per-worker loop ensures disciplined progress from plan to completion with strict phase progression and dispatch verification.

What is a per-worker execution loop in workflow orchestration?▼

A per-worker execution loop is a controlled cycle that executes one task at a time by planning, dispatching, verifying, reporting, and repeating. It coordinates workers and validates results to ensure disciplined progression through task beads.

Can I execute multiple tasks simultaneously or does the loop process one task at a time?▼

The execution loop processes strictly one task at a time to maintain controlled progress and quality control. It supports standalone mode for dispatching subagents, but phase transitions enforce sequential task completion rather than parallel execution.

How do I handle errors and validate task outcomes during automated workflow execution?▼

Error handling and outcome validation occur during the verification phase of the execution loop. The orchestrator checks task readiness, validates dependencies, confirms dispatch results, and applies guardrails before reporting to downstream beads or looping back.

Does standalone execution mode support dispatching subagents for multiple tasks?▼

Standalone execution mode supports dispatching subagents to handle tasks while maintaining consistent phase transitions. It operates alongside worker mode for direct execution, both governed by strict task readiness checks and reporting constraints.

When should I use an orchestrator for feature work pipelines instead of manual task execution?▼

Use an orchestrator for feature work pipelines when you need automated dispatching, strict phase progression, and built-in quality control. It eliminates manual worker coordination by enforcing one-task-at-a-time operation with verification and error handling.