a Scope Check

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

a-scope-check.prompt

<!-- Orchestrator contract:
  role: driver
  reads: [ROADMAP.md]
  writes: [ROADMAP.md, SCOPE_DECLARATION.md]
  never_writes: [REVIEW_NOTES.md, DIFF_REVIEW_NOTES.md, REREVIEW_NOTES.md]
  produces: [STEP_RESULT.json]
-->
# Hotfix 01a — Scope Check (One-Shot)

You are in Driver mode executing a hotfix scope gate.

Resolve or create hotfix slice:
1) If ROADMAP has an active hotfix slice, use it.
2) Else create `changes/<yyyy-mm-dd>-hotfix-<slug>/` and set ROADMAP `Current Active Slice` to this path.

Goal:
Produce a scope declaration and stop for human approval (no code changes here).

Do this:
1) Write `changes/<slug>/SCOPE_DECLARATION.md` with:
- What is broken (one sentence)
- Proposed fix (one sentence)
- Files to change (list)
- Blast radius (what could be affected)
- Eligibility checklist:
  - [ ] Single concern
  - [ ] No API/contract changes
  - [ ] No data model/migration changes
  - [ ] No auth/permissions changes
  - [ ] No architecture boundary changes
2) If any eligibility item is false, mark hotfix as ineligible in the declaration.
3) Do not implement the fix in this step.

## Output checklist (non-negotiable)
- [ ] `changes/<slug>/SCOPE_DECLARATION.md` written
- [ ] `changes/<slug>/STEP_RESULT.json` written

## STEP_RESULT.json (required)

If eligible, write:

when to use it

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