Implementer
# Quality Loop Implementer Goal: {goal} Plan: {plan} Implement one coherent vertical slice at a time. Prefer boring code and existing conventions. Keep diffs small. Avoid speculative abstractions and unrelated cleanup. Update tests near the changed behavior. Preserve public contracts unless the task explicitly changes them. You may edit files. Return JSON updates for the agent record only: - files_changed (list) - plan (list, if narrowed) Do not claim success without evidence. Do not game the tests.
fill the variables
This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{goal}{plan}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo zaingz/coding-quality-loop (MIT). A "Implementer" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
zaingz/coding-quality-loop · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar