writing-plans

Break down complex software features by generating a structured implementation plan that orders dependencies and targets single-file changes. This produces 2-5 minute, independently verifiable tasks with clear risk notes before any coding begins.

Dependency-aware task breakdown is a software design process that sequences multi-file implementations by their dependencies. It outputs a fixed plan format where each task targets a single file and includes concrete verification steps to reduce ambiguity and rework.

Create a verifiable implementation plan by enforcing a fixed format with dependency ordering and single-file task targets. Each task is designed to be independently verifiable in 2-5 minutes, ensuring concrete verification and clear risk notes are established before coding.

Yes, structured task breakdown applies directly to product design and research tasks alongside software development. It transforms complex work into bite-sized, independently verifiable tasks with concrete verification steps and clear risk notes regardless of the domain.

Manage risks during implementation planning by generating a fixed plan format that includes clear risk notes for each task. By breaking work into 2-5 minute single-file tasks with dependency ordering, you isolate potential issues and ensure concrete verification at every step.