Driver Implement

GPTClaudeDeepSeek··▲ 1,386 copies·updated 2026-07-14

driver-implement.prompt

<!-- Orchestrator contract:
  role: driver
  reads: [PLAN.md, TASK_QUEUE.md, NOW.md]
  writes: [TASK_QUEUE.md, NOW.md, DIFF_SUMMARY.md, CONTEXT.md, DESIGN_BREAK.md, PROOF.md]
  never_writes: [REVIEW_NOTES.md, DIFF_REVIEW_NOTES.md, REREVIEW_NOTES.md]
  produces: [STEP_RESULT.json]
-->
# 4. Driver — Implement

You are in Driver mode.

Resolve active slice from ROADMAP as `changes/<slug>/`.

Goal:
Implement approved major bugfix tasks without opening PR yet.

Rules:
- Follow Design Freeze.
- If design break appears, append DESIGN_BREAK and stop for reviewer loop.
- Keep NOW max 3 tasks.
- Keep TASK_QUEUE current.

Execution:
- implement NOW tasks
- refill NOW from READY tasks until done or blocked
- append DIFF_SUMMARY at checkpoint
- append PROOF when verification is run

Output checklist:
- [ ] TASK_QUEUE updated
- [ ] NOW updated
- [ ] DIFF_SUMMARY appended
- [ ] CONTEXT updated if handoff changed
- [ ] DESIGN_BREAK appended if needed
- [ ] STEP_RESULT written

## STEP_RESULT.json (required)

when to use it

Community prompt sourced from the open-source GitHub repo kylehuirevvision/repo-rails (MIT). A "Driver Implement" 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.