impl

Phase-by-phase implementation executes approved plans one stage at a time, pausing for manual verification between steps. It handles plan parsing, worktree setup, coding, automated verification, and PR creation.

Yes, interrupted implementation work can be resumed. The process supports resuming from the last completed phase, allowing you to continue coding without restarting the entire plan execution.

Interactive plan execution adapts to real-world code discrepancies. When the actual codebase differs from the approved plan, the implementation process adjusts to match the real code structure rather than failing.

Executing approved technical plans from shared directories involves reading the plan, setting up a git worktree, implementing code phase by phase, running automated verification, and creating a pull request for human review.

Yes, an approved technical plan is required. The implementation process reads plans from shared directories and executes them phase by phase, so the plan must exist and be approved before coding begins.

Implementation pauses between phases for human verification, allowing you to manually review and test the code after each stage. This ensures correctness and adaptability before proceeding to the next part of the plan.