Driver Plan
<!-- Orchestrator contract:
role: driver
reads: [AGENTS.md, SPEC.md, ARCHITECTURE.md, docs/runbook.md, ROADMAP.md]
writes: [ROADMAP.md, PLAN.md, TASK_QUEUE.md, NOW.md, CONTEXT.md, DIFF_SUMMARY.md, PROOF.md]
never_writes: [REVIEW_NOTES.md, DIFF_REVIEW_NOTES.md, REREVIEW_NOTES.md]
produces: [STEP_RESULT.json]
-->
# 1. Driver — Start Major Bugfix Slice
You are in Driver mode.
Goal:
Create a major bugfix slice packet with strict safety and rollback discipline.
Steps:
1) Create `changes/<yyyy-mm-dd>-major-bugfix-<slug>/`.
2) Update ROADMAP active slice pointer.
3) Create/initialize:
- PLAN.md
- TASK_QUEUE.md
- NOW.md
- CONTEXT.md
- DIFF_SUMMARY.md (empty template)
- PROOF.md (empty template)
4) Ensure PLAN includes incident summary, repro, impact/severity, blast radius, rollback triggers, verification, and acceptance.
5) Ensure PLAN also includes `Pre-merge Operations`.
6) Request reviewer plan pass.
Output checklist:
- [ ] slice folder + docs created
- [ ] ROADMAP updated
- [ ] 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 Plan" 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
kylehuirevvision/repo-rails · 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