implement

Automating TDD task implementation from a plan file involves using a skill that reads your plan and launches implementer agents to execute the tasks. It applies test-driven development practices to turn actionable work items into structured code with automated reviews.

Running multiple coding tasks in parallel using isolated git worktrees is supported when safe isolation rules are met. The process launches parallel implementer agents from your plan, creating a separate worktree per task to prevent branch conflicts during execution.

The best way to coordinate parallel code tasks with test-driven development is through plan-driven orchestration that enforces pre-launch checks and per-task commits via squash merges. This approach safely launches parallel agents while maintaining a structured post-implementation review cycle.

A post-implementation review and documentation cycle for automated coding tasks triggers automatically after task completion. It initiates a review of the implemented code, applies potential fixes, and updates documentation to ensure the final output aligns with the original plan requirements.

You do not strictly need a plan file to start automated TDD-based task implementation. The process accepts either a structured plan file for orchestrating multiple parallel tasks or a single task description to drive sequential implementation.

You should avoid running parallel implementer agents for code generation when project isolation rules are not satisfied. If safe worktree isolation cannot be guaranteed, the system defaults to running tasks sequentially to prevent branch conflicts and maintain codebase integrity.