What problem does it solve? Turning an approved development plan into actual code changes is error-prone: steps get skipped, verification is forgotten, scope creeps beyond the plan, and changes land directly on main. This Skill operationalizes the approved plan in docs/current-plan.md by executing each step in order with mandatory verification, branch isolation, and a closing review pass. ## Core Features & Use Cases - Branch-per-task workflow: Derives a kebab-case branch name from the plan topic, syncs main, and confines all changes to that branch. - Stepwise execution with verification: Reads the plan's status table, implements each pending step, runs the corresponding tests/build, and updates plan status after every step. - Blocking and scope control: Stops and reports when encountering unconfirmed blocking items, plan/code conflicts, or out-of-scope changes instead of silently expanding scope. - Acceptance and review closure: Validates every acceptance criterion against concrete tests, runs affected regression tests, updates the changelog, invokes the review-with-docs audit, and opens a PR via gh when zero blockers remain. - Use Case: After plan-designer produces an approved development plan, tell the agent to execute docs/current-plan.md and receive a reviewed, tested pull request on a dedicated feature branch. ## Quick Start Ask the agent to execute docs/current-plan.md according to the approved plan and report progress step by step.