Task Planning

Overview

Produce thorough implementation plans written for an engineer with zero familiarity with the codebase and unreliable design instincts. Spell out everything: which files to touch per task, exact code, testing procedures, relevant documentation, how to verify each step. Deliver the plan as granular, self-contained tasks. DRY. YAGNI. TDD. Frequent commits.

Assume the engineer is technically competent but knows almost nothing about the project's tooling or problem domain. Assume their test design skills are weak.

Announce at start: "I'm applying the task-planning skill to build the implementation plan."

Context: This should run in a dedicated worktree (created during the intent-discovery phase).

Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md

The Prime Directive

NO IMPLEMENTATION WITHOUT A PLAN FIRST