team-implement

Automating design-to-code implementation requires reading the TASK_FILE sections for Brief, Design, and Decision Log to guide tiered workflows and update Implementation Notes. This ensures your coding phase aligns directly with the initial design scope and success criteria.

A tiered workflow for team coordination categorizes implementation tasks into S, M, and L sizes to delegate modules to subagents while keeping a Lead informed. It structures execution by reading design guidance and posting progress updates.

To maintain a decision log and implementation notes during code delivery, automate updates to the TASK_FILE as modules are implemented. This records architectural choices and progress, ensuring full traceability from design to code.

Yes, you can coordinate subagents for large implementation tasks using tiered plans to delegate S, M, and L sized work. The Lead remains informed through automated In Progress updates and continuous Decision Log synchronization.

Yes, team-implement operates without external dependencies to track implementation progress. It relies entirely on reading and updating the internal TASK_FILE structure to manage the transition from design to code and record decisions.

Using a task file for the design-to-code transition enforces reading scope and success criteria before execution, unlike manual tracking. It automatically updates Implementation Notes and the Decision Log to maintain strict project traceability.