implement-task-code

You can implement planned tasks using strict test-driven development by validating task prerequisites, writing failing tests first, writing minimal code, and verifying the entire project before committing changes. This ensures tested code from a work queue.

Yes, task tracking and feature branch management are supported. The workflow updates the plan file, manages the shared feature branch state, and pauses for human approval before committing any code changes.

Tooling discovery identifies the project's specific test, lint, format, and build commands. This ensures every check during test-driven development uses the real toolchain rather than guessed commands.

Yes, you need plan files, design documents, and a task status tracker. The process checks prerequisites, conflicts, and eligibility from these tracked items before any implementation work begins.

Task validation checks the task status tracker, prerequisites, conflicts, and eligibility before work begins. This ensures the specific implementation-plan task is ready for development on the shared feature branch.

Strict TDD for task implementation is not suited for projects lacking plan files, design documents, or tracked prerequisites. It requires a structured work queue and a shared feature branch to coordinate implementation work effectively.