worker

Execute beads autonomously within a track while maintaining context via Agent Mail.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mthangtr/groaly --skill worker-mthangtr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/mthangtr/groaly/tree/main/.claude/skills/worker
Command: npx skills add https://github.com/mthangtr/groaly --skill worker-mthangtr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Worker Skill enables autonomous bead execution within a track, preserving bead-to-bead context through Agent Mail and reporting progress to the orchestrator, so teams can scale multi-bead workflows without losing state.

Core Features & Use Cases

  • Autonomous bead loop: Repeats a structured track loop for each bead, including reading context, working on the bead, and reporting completion.
  • Context persistence: Maintains cross-bead state via Agent Mail to ensure continuity across beads.
  • Orchestrated reporting: Integrates with the orchestrator to surface progress and completion statuses.

Quick Start

Start a new track and watch the Worker autonomously execute beads, persist context via Agent Mail, and report progress to the orchestrator.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I maintain context persistence across asynchronous workflow steps?▼

Context persistence across asynchronous workflows is maintained by saving bead-to-bead state via Agent Mail, ensuring continuity and structured communication throughout multi-bead track execution.

How does autonomous bead execution report progress to an orchestrator?▼

Autonomous bead execution reports progress to an orchestrator by using Agent Mail to send structured messages, tracking completion statuses and surfaced progress throughout the track lifecycle.

Can I scale multi-bead workflows without losing track execution state?▼

Multi-bead workflows can scale without losing state by autonomously executing beads within a track while preserving cross-bead context and reporting completion statuses to the orchestrator.

What is the best way to automate track loops with asynchronous messaging?▼

Automating track loops with asynchronous messaging is best handled by a structured bead lifecycle that repeats setup steps, reads context, executes beads, and saves state via Agent Mail.

Do I need an orchestrator to manage autonomous bead workflows?▼

An orchestrator is needed to receive structured progress reporting and completion statuses from the worker, coordinating the overall multi-bead track execution and asynchronous messaging.

Why does cross-bead context get lost in multi-bead workflows?▼

Cross-bead context gets lost in multi-bead workflows without context persistence mechanisms like Agent Mail, which maintains state continuity by saving and reading context during each track loop iteration.