project-worker

To automate work order execution, you provide the project root path and specific work order IDs. The agent then reads local indices and applies development rules to unblock, implement, and verify tasks autonomously.

Autonomous project execution handles work orders without constant human intervention by automatically resolving blockers, updating work order indices, and managing project-level status reporting throughout the task lifecycle.

Yes, autonomous task management requires access to project-specific rules files and work order queues within your project directory to ensure consistent, autonomous task completion and lifecycle management.

You dispatch the agent by activating it with the absolute path to your project root and the target work order IDs, allowing it to check dependencies, execute implementation, and document results.

Managing fragmented project execution is best handled by an autonomous worker that processes unblocked work orders inline, automatically updating status indices and managing blocker resolution without requiring constant human intervention.

The autonomous worker is limited by its dependency on local project indices and specific rules files; without access to project-specific work order queues and rules, it cannot ensure consistent task completion.