implement_plan

You can automate plan implementation by reading the plan artifact, updating checkboxes for completed items, transitioning status from active to implemented, and running verification criteria at each phase to ensure all defined success criteria are met.

Translating a plan into concrete changes requires reading the original ticket and referenced files, enforcing status transitions, and coordinating automated checks to apply modifications phase by phase against the approved plan artifact.

Yes, the implementation process pauses for human verification between phases, surfacing any issues for guidance before proceeding to the next phase to ensure manual validation of automated changes.

Automated plan implementation tracks progress by reading and updating plan artifacts, marking completed items, enforcing status transitions from active to implemented, and coordinating automated checks throughout the phase lifecycle.

Running verification milestones involves coordinating automated checks and manual verification steps at phase boundaries, pausing implementation to validate that all defined success criteria are met before transitioning to the next phase.

You need an approved plan document containing defined phases, success criteria, and referenced files, which the system reads to begin translating the approved plan into concrete changes through automated phase execution.