writing-plans

To break down a feature specification into TDD-sized steps, generate a detailed implementation plan that enforces atomic actions, mandates writing tests first, and requires exact file path referencing for zero-context execution. This ensures all tasks are clearly defined before coding begins.

The best way to structure an implementation plan for test-driven development is to define each step as a single, independent action, such as writing a failing test or implementing minimal code, ensuring clarity and executability before any code is written.

To create an implementation plan for zero-context execution by an AI agent, specify precise file paths for creation, modification, and testing, and break down tasks into atomic actions that enforce test-first development principles.

You should use task breakdown for multi-step software development workflows because it addresses the issue of vague or overly large tasks by ensuring clarity and executability, structuring development into small, actionable, test-driven steps before coding begins.

Yes, this implementation plan enforces test-first development by mandating that writing tests first occurs within each atomic task step, ensuring structured software development workflows that follow Test-Driven Development principles.

A limitation of using atomic task definition for implementation planning is that it requires exact file path specifications and detailed specifications upfront; without precise inputs, the generated plan cannot ensure zero-context execution for the developer or AI agent.