writing-plans

An implementation plan for complex software features is generated by breaking down multi-step tasks into bite-sized instructions. This approach emphasizes test-driven development, frequent commits, and exact file paths to ensure clear execution.

Breaking down development tasks for engineers with limited context requires generating detailed, step-by-step plans. This method assumes minimal prior codebase knowledge and provides explicit instructions for writing failing tests and minimal implementations.

Test-driven development integrates into a task breakdown plan by prioritizing failing tests first, followed by minimal code implementation. This structured planning ensures engineers follow a strict TDD workflow throughout the feature lifecycle.

Implementation plans support both subagent-driven and parallel session execution workflows. This allows multiple engineering streams to work simultaneously from the same detailed, step-by-step instructions.

A detailed implementation plan is needed when onboarding new engineers or tackling complex features. It solves the challenge of providing clear, actionable steps for multi-step tasks by assuming minimal prior domain knowledge.

Yes, this planning approach is designed for contextual onboarding and explicitly assumes minimal prior knowledge of the codebase. It provides exact file paths and clear instructions to guide engineers through the implementation.