writing-plans

To break down complex software features into executable tasks, specify 2-5 minute steps with exact file paths, implementation details, and verification commands. This planning approach ensures junior developers can execute multi-step development work with minimal context.

Task breakdown in software engineering planning is the process of decomposing multi-step development features into bite-sized, fully specified tasks. It includes exact file paths, implementation details, and concrete testing steps to guide contributors through execution.

Referencing Linear issue context is required to align planning with project workflows. The task breakdown process also requires adherence to CLAUDE.md conventions to ensure generated steps match existing project standards and documentation.

The best way to create sprint-ready plans for junior contributors is to divide complex work into 2-5 minute tasks with explicit file paths and verification steps. This enables end-to-end planning and clear task delineation across software projects.

Yes, TDD workflow planning includes concrete testing and verification commands for each task. Breaking work into bite-sized steps enforces explicit verification alongside exact file paths and implementation details to validate task completion.

Detailed task breakdown should be avoided for single-step or trivial changes where explicit file paths and verification commands add unnecessary overhead. It is designed for multi-step development and complex features requiring clear task delineation.