micro-task-workflow

To prevent context exhaustion during task decomposition, enforce a fixed context budget across micro-tasks with explicit commit points. This approach structures work into startup, productive, and safety phases to maintain context and ensure incremental progress.

A micro-task workflow is a process that breaks down larger tasks into smaller, scoped units managed within a strict context budget. You should use it for issue-based development or planning sprints where maintaining context is critical and context exhaustion frequently disrupts progress.

You can set up a per-issue worktree strategy by running the startup script from your project root. This creates isolated worktrees for each issue, enabling structured commits and auditable progress tracking while adhering to the defined context budget constraints.

Yes, a context budget workflow includes an escape hatch protocol to handle situations where the context budget is exhausted before a micro-task is complete. This protocol ensures incomplete work is safely saved and auditable for the next session.

Managing a micro-task context budget requires specifying operational constraints such as startup overhead, a productive work share, and a safety margin. These constraints divide your context window into distinct phases to enforce scope control and guarantee incremental progress.