oat-project-implement

Automating sequential task execution requires parsing a defined plan.md file and processing each task in order. This skill enforces Test-Driven Development discipline while systematically building features, running tests, and committing code for each task sequentially.

TDD enforcement during code implementation works by integrating Test-Driven Development principles directly into the workflow, ensuring tests are written and executed before implementation progresses. It tracks task verification, commits, and blockers through artifact updates.

Yes, you need Git to manage project implementation tasks sequentially, as this skill requires Git for version control. It manages commit history for the defined project scope by committing code after each task passes verification.

The best way to track implementation progress and state is by updating predefined OAT artifacts like implementation.md and state.md. This skill automatically updates these files to reflect task execution progress, commits, and blockers throughout the workflow.

No, you cannot skip tasks or execute them out of order, because this skill executes tasks defined in the plan sequentially. It maintains strict order while managing task execution, verification, and commit history for the defined project scope.