forge:implement

Automating feature implementation after plan approval requires a pipeline that transforms the plan into tested code. This skill orchestrates that flow by creating a dedicated worktree, running coder steps, dispatching reviewers, and handling revision loops.

The FORGE implement pipeline is an automated workflow that executes approved plans end-to-end. It creates isolated worktrees, validates plans, synthesizes code via coder and reviewer steps, manages revision loops, and prepares a gate2 decision for user confirmation.

Handling blockers during an automated implementation workflow involves running scope checks and revision loops within the pipeline. The process detects blockers, validates changes against the approved plan, and iterates through coder and reviewer synthesis until safe.

Using this implementation pipeline requires Gate #1 approval as a prerequisite. The automation applies specifically when an approved plan exists and needs transforming into a concrete, tested implementation within a dedicated worktree.

Finalizing an automated code implementation and review cycle requires a user-confirmed gate2 decision. After the pipeline completes coder synthesis, reviewer dispatch, and revision loops, it prompts the user to either approve and finalize changes or discard them.

Automated feature implementation needs a dedicated worktree to isolate run creation, coder work, and reviewer steps from the main branch. This ensures safe, approved changes by containing the synthesis and revision loops within a separate workspace.