writing-plans

To turn complex requirements into an implementation plan, you provide a feature specification and receive a task-by-task breakdown with explicit file paths, tests, and milestones for reproducible execution.

The best way to break down multi-step features for collaboration is generating bite-sized tasks of two to five minutes each with clear success criteria, explicit file boundaries, and version-controlled handoffs.

To create zero-context design handoff documentation, transform specifications into organized implementation plans that include exact tasks, complete file paths, required tests, and explicit milestones for immediate execution.

Yes, this planning approach supports subagent-driven development and TDD by generating bite-sized task templates with explicit test definitions and clear task boundaries for automated or test-first execution.

Yes, you can use this for version-controlled task breakdowns in software engineering, as it satisfies frontmatter-driven metadata and provides reproducible, task-based implementation plans for cross-team handoffs.

Implementation plans lack clear boundaries and traceability when specifications are not transformed into organized, bite-sized tasks with explicit files, tests, and milestones for reproducible execution.