code-implementer

Automating code implementation from a technical plan requires executing phase-based changes and running verification commands before progressing. This skill reads approved plans, applies modifications, runs build and test validations, and commits changes only when verification passes.

A verification-first workflow for software implementation ensures that build and test commands must pass before any code phase is marked complete. This strict loop prevents progressing to the next phase until the current changes are validated, enforcing disciplined plan execution.

Executing phase-based development plans involves reading unchecked phases, applying code changes, and running verification tests. Upon successful verification, the implementation results are committed to Git with descriptive messages and the session ticket is updated to reflect progress.

Yes, automated testing can block code progression by enforcing a strict verification check after each phase. The implementation loop halts and will not proceed to the next step until the required build and test commands successfully pass validation.

Ensuring traceable changes from session plans through Git commits requires linking phase execution to version control. This skill applies plan changes, validates them through automated testing, and commits the results with descriptive messages to maintain a clear project history.

Strict plan-to-code execution relies on automated verification rather than manual debugging between phases. It applies changes, runs build and test commands, and only marks the phase complete if verification passes, otherwise halting the implementation loop.