worker

Autonomous workflow execution is achieved by processing individual tasks sequentially while passing context between them via Agent Mail, ensuring each step retains the information needed to complete the larger operation.

Bead-to-bead context persistence works by using Agent Mail to pass information from one executed task to the next, ensuring autonomous agents retain necessary context throughout a defined workflow track.

To execute the next bead in a track, invoke the worker skill with the specific track number and project path, allowing it to autonomously process the task and report progress to the orchestrator.

Yes, autonomous task execution leverages preferred tools defined in AGENTS.md, allowing the agent to integrate specific development tools required for completing coding and testing tasks within an epic.

The best way to report progress is through built-in orchestrator updates, where the agent sends status reports on each individual task and the overall workflow track after autonomous execution completes.

Use autonomous agent execution for deterministic task sequences when you need to automate repetitive coding tasks, implement changes, and run tests within a software development epic without constant human intervention.