dev-do

What problem does it solve? Turning a written implementation plan into actual code changes is slow and error-prone when done manually: phases get skipped, commits lose scope, and verification steps are forgotten. This Skill acts as a staff-level engineer that reads a plan.md produced by dev-plan and drives it to completion with disciplined, verifiable execution. ## Core Features & Use Cases - Phase-by-phase execution: Implements each plan phase, runs its verification commands, and creates exactly one path-limited conventional commit per phase with post-commit identity checks. - Durable progress tracking: Updates plan.md statuses and a Progress Log with PENDING/COMMIT entries so interrupted runs can be safely recovered on re-invocation. - Controlled autonomy: Runs all pending phases back-to-back by default, with optional max_subagents parallel fan-out and checkpoint_every yield boundaries for user review. - Use Case: After drafting a plan with dev-plan for a multi-file refactor, invoke this Skill with the slot number to have every phase implemented, tested, and committed locally — without pushing or opening a PR. ## Quick Start Run the dev-do skill on slot 2 to execute today's plan and commit each completed phase locally.