plan-driven-implementation

name: plan-driven-implementation description: Execute attached plan documents in this repo while keeping existing TodoWrite items synced. Use when the user says to implement an attached `.plan.md` as specified, not edit the plan file, avoid recreating todos, and work through the plan end to end.

Use this skill when the user provides or references an attached plan document and asks to implement it directly.

Common signals:

Read the attached plan and inspect the current code surface it touches.
Do not edit the plan file unless the user explicitly changes that instruction.
Do not recreate TodoWrite items that already exist.
Mark the first relevant existing todo in_progress before substantial implementation work.
Keep exactly one todo in_progress at a time.
As each plan section is finished, mark that todo completed and move the next one to in_progress.
Implement the plan in the same order unless the code forces a small reordering.
Validate before finishing: run focused checks first, then broader non-E2E validation if the change touches shared paths.
Run ReadLints on the files you changed after substantive edits.

Use uv run for pytest and other Python commands
Do not start the FastAPI server, systemd service, E2E tests, or live curl requests unless the user explicitly asks
Treat existing uncommitted user changes as real context; work with them instead of reverting them
If the plan affects auth, routes, or deployment docs, include a coordination note in the final response if another surface still needs follow-up

Summarize the implemented outcome, not the plan text
List the validation you actually ran
Call out anything you could not validate
Mention any required coordination or natural next step only if it remains outside the requested scope