planning-patterns

Task-breakdown converts vague goals into bite-sized, 2-5 minute steps using test-driven development. Each step specifies concrete actions—write failing test, implement code, verify—with explicit file changes, test scenarios, and acceptance criteria, enabling zero-context engineers to execute without ambiguity.

Spec-based planning combines TDD principles with DRY and YAGNI to eliminate vague instructions. Create a plan header with goal, architecture, and tech stack, then enumerate tasks as specific, verifiable actions—each touching named files, defining test scenarios, and stating acceptance criteria for transparent progress.

Implementation planning requires a header template covering goal, architecture, and prerequisites, followed by concrete task steps. Each step must be testable, specify touched files and commit actions, include test scenarios, and state acceptance criteria—eliminating vagueness so unfamiliar engineers verify and complete work independently.

Task-driven planning applies DRY and YAGNI principles to scope control. By committing to bite-sized, test-driven steps with explicit acceptance criteria and no vague instructions, teams avoid over-engineering, reduce rework cycles, and maintain focus on verified, deliverable increments rather than speculative features.

Specificity requires naming files touched, stating test scenarios to run, defining verifiable acceptance criteria, and describing concrete actions—not aspirations. Test-driven steps create checkpoints; each passes or fails objectively, eliminating interpretation and enabling any engineer to proceed or flag blockers with certainty.