SomtoUgeh Resolve Todo Files
Finish the requested todo files completely while preserving dependency order and avoiding overlapping edits.
Workflow
- Find the todo directory from the user's path or repository convention. Read every candidate before changing code.
- Build a dependency graph. For each todo, record prerequisites, owned files or modules, completion criteria, and verification.
- Show a Mermaid graph only when it makes non-trivial dependencies easier to understand.
- Execute ready items in waves. Run independent items concurrently only when the active runtime permits delegation. Cap a wave at the available worker slots and normally at three workers.
- Give each worker exclusive file or module ownership and tell it that other workers share the checkout. Keep overlapping or dependent items in the main agent or in later waves.
- After each wave, inspect the integrated diff, resolve interactions centrally, and run the focused checks required by those todos.
- Update a todo's status or rename its file only after its acceptance criteria pass. Preserve the repository's existing status and naming convention.
- Report completed, blocked, and skipped items with evidence.
Git Boundary
Do not infer permission to commit or push from a request to resolve todos. Stage, commit, or push only when the user has already authorized that action. If authorized, stage centrally after worker changes are integrated; workers must not create competing commits.
Stop and ask only when a real dependency, conflict, or missing product decision cannot be resolved from the repository or the user's existing instructions.