implementing-tasks

Task plans are converted into executable code by generating implementation files and corresponding tests from prompts, creating incremental work items, and updating task statuses as work progresses.

Automated task implementation updates task statuses by setting them to READY_FOR_TESTING or READY_FOR_REVIEW once code generation and test execution for the incremental work items are complete.

The best way to implement tasks from .plans prompts is by reading the implementation prompt, creating incremental work items as Todo steps, generating code and tests, and updating the task status accordingly.

Yes, research agents are launched automatically when blockers are encountered during the task implementation process to investigate issues and unblock code generation progress.

Yes, this task implementation workflow requires task files to be placed in an implementation/ folder within the .plans directory structure to trigger the code generation and status update process.

You need to generate code and tests from plan files when a task prompt sits in an implementation folder and requires building, testing, and documentation to produce concrete deliverables with traceable progress.