b Implement

GPTClaudeGemini··▲ 420 copies·updated 2026-07-14

b-implement.prompt

<!-- Orchestrator contract:
  role: driver
  reads: [SCOPE_DECLARATION.md, PLAN.md, README.md]
  writes: [PROOF.md]
  never_writes: [REVIEW_NOTES.md, DIFF_REVIEW_NOTES.md, REREVIEW_NOTES.md]
  produces: [STEP_RESULT.json]
-->
# Hotfix 01b — Implement (One-Shot)

You are in Driver mode executing approved hotfix implementation.

Resolve active slice from ROADMAP and use it as `changes/<slug>/`.
Read `SCOPE_DECLARATION.md` first.

Read optional orchestrator input block:
- `[ORCHESTRATOR_INPUT] ... [/ORCHESTRATOR_INPUT]`
- If approval is not explicit, stop with `NEEDS_INPUT` asking for explicit APPROVE.
- If approval is explicitly `REJECT`, do not implement and return a `REJECTED` step result.

Goal:
Implement the smallest safe fix and run verification.

Steps:
1) Implement minimal fix only within approved scope.
2) Run verification commands from README/scripts/CI.
3) Write or append `PROOF.md` with:
- scope declaration summary
- commands run and PASS/FAIL
- failures and suspected root cause if any

Output checklist (non-negotiable):
- [ ] fix implemented minimally
- [ ] `changes/<slug>/PROOF.md` updated
- [ ] `changes/<slug>/STEP_RESULT.json` written

## STEP_RESULT.json (required)

If approvals are missing:

when to use it

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