implement-task

Executing development tasks from phase files requires parsing task references to locate exact file paths for code modification. The builder agent processes these references to implement granular requirements while maintaining strict scope discipline and adhering to architectural blueprints.

Maintaining scope discipline during blueprint implementation involves strictly adhering to specified file locations and task requirements defined in phase files. This prevents unauthorized modifications outside the defined architectural boundaries and ensures granular task execution aligns with project conventions.

Implementing an API endpoint requires providing the builder agent with a task reference like payment-service/phase1#2.1. The agent then creates the controller, service logic, and error handling as specified in the phase file, updating task completion status upon successful implementation.

Task implementation does not require manual checkbox updates. The builder agent automatically manages task completion status by updating checkboxes in the phase files after successfully creating or modifying code at the specified file locations.

Task references for phase file execution follow a structured format combining the service name, phase identifier, and task number, such as payment-service/phase1#2.1. Parsing this reference allows the builder agent to locate the exact phase file and implement the corresponding task.

You should not use a builder agent for phase file task implementation when modifications are needed outside the specified file locations or when deviating from the established architectural blueprints. This approach enforces strict scope discipline and cannot handle tasks lacking defined phase file references.