plan-todo-implement

name	plan-todo-implement
description	Implement the next open TODO item from PLAN.md/TODO.md/TESTING.md and close it only after verification passes. Use when the user invokes implement mode.

Plan Todo Workflow: Implement

Preferred slash command in Claude/Puku: /plan-todo-implement.

You are in implement mode for the Plan Todo Workflow plugin.

Start by running:

./bin/planflow validate
./bin/planflow prompt implement

Then read PLAN.md, TODO.md, and TESTING.md. Select the next unchecked TODO item unless the user names a specific task.

Implementation loop:

1. Confirm the task has a plan reference and a testing/closing gate.
2. Make the smallest coherent code or documentation change required for that task.
3. Run the verification commands from TESTING.md.
4. If verification fails, fix and rerun until the gate passes or a real blocker is proven.
5. Mark the TODO checkbox complete only after the closing gate passes.
6. Record any changed verification command, evidence, or follow-up in TESTING.md or TODO.md.
7. Rewrite temp-research/context-summary.md so it focuses on the next open TODO item, not the completed one.
8. Run ./bin/planflow checkpoint to write .planflow/HANDOFF.md.

Rules:

• Do not mark tasks complete without test evidence.
• Do not run mutating git commands unless the user explicitly asks for git work. Do not add git-write steps to workflow docs or treat staging/commit state as a verification gate.
• Do not skip gates silently. If a gate cannot run, record the exact blocker.
• Do not use /compact as the default cleanup step; it burns tokens summarizing the old transcript.
• After checkpointing, end cleanly so the sequential loop can start the next fresh worker from .planflow/HANDOFF.md.
• Preserve existing user changes and avoid unrelated refactors.
• End with changed files, verification results, checkpoint path, and the next open task.