Planning and Task Breakdown

Overview

Decompose work into small, verifiable, disk-persisted tasks with explicit acceptance criteria. Plans are written to .tasks/ so they survive context resets, session boundaries, and compaction. Every task is small enough to implement, test, and verify in one focused session (target: 5–15 minutes of agent work).

When to Use

• You have a spec and need to break it into implementable units
• A task feels too large or vague to start
• Work spans multiple sessions or agents
• Implementation order is not obvious
• You need to communicate scope to a human before proceeding

When NOT to use: Single-file changes with obvious scope, or when the spec already contains well-defined tasks.