code

To implement code automatically, provide a plan.md file path to trigger phased execution. The system reads the plan, spawns an implementer subagent for each phase, and chains review, test, debug, and commit agents via post-tool hooks.

Agent orchestration uses PostToolUse hooks to automatically chain code-reviewer, tester, debugger, and git-manager agents after implementation. Each agent activates sequentially with QA and retry logic, removing manual pipeline management.

Yes, phased development workflows execute one plan phase at a time and include automatic git commits. The git-manager agent commits changes when each phase completes successfully after passing review and testing.

Plan-driven implementation requires an existing plan.md file path as an argument. Say "start coding" and provide the path; the system handles implementation, review, testing, debugging, and commits without further manual input.

Yes, debugging and retries are handled automatically during implementation. A debugger agent activates through hook-driven orchestration, applying QA and retry logic to resolve issues before the git-manager commits the code.

Use automated code implementation when you have a detailed plan.md ready and want to skip manual pipeline steps. It suits phased development workflows where teams need coordinated implementation, review, testing, and git commits.