decidelisted

# Decide Research the question → reach a recommendation → document it as an ADR. ## Auto-invocation triggers - User asks to "decide between X and Y", "research and decide", "pick a tool/approach and document it" - After `adr-gap` flags an undocumented decision that needs retroactive capture - When starting a significant architectural choice (ORM, framework, deploy target, caching strategy) ## Workflow ### Phase 1 — Research and Recommend (always) Invoke `research-and-decide` on the decision question. Output: options evaluated, recommendation with rationale, risks, rejected alternatives. **Proceed:** if research produces a clear recommendation. **Stop:** if research returns "no clear winner" or "requires more constraints" → emit "Phase 1 inconclusive: [reason]. Provide additional constraints before proceeding to ADR." Wait for human input. Do NOT write an ADR for an undecided question. ### Phase 2 — Document the Decision (at proportional fidelity, if Phase 1 succeeds) Invoke `adr-write` using Phase 1's output. adr-write applies the record gate: full ADR only when a gate trips (public-facing repo, sprint-level undo cost, recurring-alternative rejection, post-incident); otherwise one status-prefixed line in the repo's `DECISIONS.md`. Pass to adr-write: decision title, context (the question + why it matters), chosen option + rationale, consequences, and alternatives considered. Output: ADR file at `docs/adr/YYYY-MM-DD-<slug>.md`, or one line in `DECISIONS.md`. **Done