Intake

# Off-Roadmap Feature — Intake Gate

## Routing note
- Use `prompts/7-roadmap-review/01-roadmap-review.md` if you are broadly reworking roadmap priorities rather than evaluating one specific feature.

## Workflow for “off-roadmap feature”
### Phase 0: Intake gate (fast)
Create a tiny intake doc and force a decision:
changes/<date>-intake-<slug>/INTAKE.md
INTAKE.md should answer:
what is it, who cares
why now (what it unlocks)
cost rough order (S/M/L)
risk (touches auth/data/contracts?)
does it replace a roadmap item or add new scope?
Decision: accept, reject, or park.
### Phase 1: If accepted, update the roadmap first
Don’t start coding until you update the roadmap. Otherwise your repo’s “truth” is fake.
Add a milestone to ROADMAP.md with status [NEXT] or [PARKED]
If it changes goals/non-goals materially, update SPEC.md too
If it forces architecture changes, add an ADR
### Phase 2: Then run the normal slice workflow
Now it’s just another milestone:
start slice packet
plan review
implement
diff review
verify (CI)
PR
release + hygiene
## Keep it simple with one rule
If it isn’t in ROADMAP.md, it doesn’t get a slice folder.
That’s how you prevent chaos.

## Reusable prompt: off-roadmap feature intake
You are Codex.

I want to add a new feature that is NOT currently on ROADMAP.md. Run an intake gate and decide whether it should enter the roadmap.

Steps:
1) Ask me only the minimum questions (max 5) needed to define:
- user + problem
- success criteria
- urgency / why now
- risks (auth/data/contracts)
- rough size (S/M/L)
2) Create `changes/<yyyy-mm-dd>-intake-<slug>/INTAKE.md` with:
- Summary (what/why)
- Scope (in/out)
- Risks + mitigations
- Rough size + dependencies
- Recommendation: ACCEPT / PARK / REJECT (with 2–4 bullets why)
3) If ACCEPT:
- Propose the exact ROADMAP.md milestone entry (title, objective, acceptance)
- Note whether SPEC.md or ARCHITECTURE.md / ADR needs updating
4) Stop. Do NOT start implementation until I confirm ACCEPT.

Output:
- INTAKE.md written
- Proposed ROADMAP entry (if ACCEPT)
- The 1–2 next steps to start the slice (but don’t do them yet)

If you want it even more ruthless, add: “If ACCEPT, specify what existing roadmap item gets delayed.” That forces tradeoffs instead of infinite scope creep.