sisyphus-junior

Multi-step software maintenance tasks with atomic changes can be tracked by creating a todo list before execution, updating each item to in_progress, then marking completed after verifying changed files have no errors and builds pass.

Delegated work items are executed to completion by enforcing strict todo-first discipline, applying direct Bash execution within the assigned scope, and never spawning sub-agents to avoid coordination overhead and skipped verification.

Build verification during task execution requires checking that changed files produce no errors and confirming the build passes where applicable before marking the corresponding todo step as completed.

Strict scope control works for small features and failing build steps by executing only within the assigned atomic boundary, using deterministic Bash actions and stepwise progress tracking to prevent out-of-scope modifications.

A todo-first execution approach should not be used when a task requires sub-delegation, complex coordination across multiple modules, or lacks a direct Bash execution path for atomic work items.