badlogic/claude-commands

Todo Implementation System

Human-agent collaborative workflows for transforming vague todos into implemented features in ~150 LOC of Markdown.

This workflow is meant for engineers who want to stay in control of and informed about their code base, using agents to do the tedious work, and their brain for the hard parts.

Two workflows available:
- todo-worktree.md: Full task isolation using git worktrees, separate branches, and incremental commits. Best for complex features or when working on multiple tasks in parallel.
- todo-branch.md: Simpler workflow on current branch with single commit at completion. Best for quick fixes, single-task focus, or when worktrees aren't desired.

Problems this solves:
- Breaking vague ideas into well defined problem descriptions and concrete implementation steps
- Preventing agents from making unauthorized changes or expanding scope
- Efficient context usage by providing agents only task-relevant information
- Full isolation of feature work (with worktrees) or simple staging workflow (without)
- Resuming interrupted work without losing context or progress
- Traceable feature development history with meaningful commits and pull requests

Problems this does not solve:
- "Claude, build me Uber for dogs"
- Slop in your code base generated by an army of unsupervised agents in the cloud
- Merge conflicts

Why this approach:
- Zero dependencies, pure markdown + git + shell commands
- Easy to understand, modify, and transfer between any coding agent
- No vendor lock-in, maximum transparency and simplicity

How it works

Both workflows follow the same state machine pattern with slight variations. Read todo-worktree.md or todo-branch.md to understand the full flow and adapt it to your needs.

At its core, each workflow is a state machine that…