writing-implementation-tasks

To break down a software feature into implementation tasks, decompose the work into atomic, single-commit units with clear dependency ordering and executable verification steps. This creates a structured markdown file outlining each step from data modeling to integration testing.

An implementation plan for spec-driven development is a structured markdown task breakdown that divides features into independently verifiable tasks. It defines task dependencies, scope, and verification commands to ensure a logical and efficient development flow.

Define task dependencies and implementation order by analyzing interdependencies between decomposed tasks. Generate a structured breakdown that sequences atomic tasks logically, ensuring each step has clear scope and executable verification commands before moving to the next.

Yes, you can use this task breakdown approach for agile workflow decomposition. It generates agent-optimized task lists with atomic scope and dependency ordering, fitting agile development by ensuring each task is independently verifiable and suitable for a single commit.

The implementation task breakdown uses a structured markdown format with specific sections for progress tracking, task details, scope, and verification commands. It generates a tasks markdown file to guide the development flow.

You need to generate an implementation task breakdown when starting a new feature or when user mentions work decomposition, implementation plan, or spec-driven development. It helps manage complex features by creating a clear, ordered path of independently verifiable tasks.