On any failure (non-zero exit, or "status":"error" in the JSON) print ⚠️ <error.message> and stop.

If file editing is unavailable in the current mode, print ⚠️ Agent cannot write files in this mode. Switch to a mode with write access. and stop.

Steps

Context. Run .agents/skills/pflow-task-implement/scripts/implement-context.sh → JSON {status,current_task,plan_file}. Implement only current_task.
Review. Read plan_file critically. If a step is ambiguous, contradictory, or has a blocking gap, stop and ask — never guess. Read .agents/skills/pflow-task-implement/references/clean-code.md and .agents/skills/pflow-task-implement/references/solid.md and apply them while writing code.
Execute. Implement each step in order, exactly as written — no extra refactors, tests, or features. Write correct, readable, duplication-free code that matches the codebase.
Verify. Run the check the plan specifies for each step; if none, confirm by reading back the change. A failing check is work, not a blocker: fix it and re-run until it passes — even if the fix is outside this task's scope. Stop and ask only when the failure exposes an unresolvable gap or contradiction in the plan.
Confirm. When every step is done and covered, reply in the Format below.

Gotchas

Reply only in this format. No summary of what was done, no extra prose.