decide-nowlisted

# decide-now Make the right call faster by grounding the decision in what's actually happening — not in generic best practices. ## decide-now vs /decide | | decide-now | /decide | |---|---|---| | **When** | Answer depends on current context | One-time architectural bet | | **Speed** | Fast (minutes) | Thorough (research phase) | | **Output** | Chat verdict | ADR file | | **Examples** | "merge now or wait?", "fix or defer?", "A or B for this task?" | "which ORM?", "which deploy target?" | Rule of thumb: if the answer would change depending on what's in memory / git / plans / PRs right now → decide-now. If future agents need to know the decision was made → /decide. ## Workflow ### 1. Load relevant context Don't read everything — scan for what the question actually needs. Common sources: | Question type | What to load | |---|---| | Merge / PR readiness | `gh pr view <N>` CI status, open review threads, CodeRabbit state | | Prioritization | Memory index, open issues, active plans, recent commits | | Approach selection | Recent ADRs, CLAUDE.md constraints, active plans, memory | | Bug fix vs defer | CI state, PR stack, issue severity, what's in flight | | Dependency on external state | Handoff at `~/.claude/handoffs/<project>/latest.md` | Always check: **CLAUDE.md hard rules** — a rule there can override everything else. When checking reviewer-comment rules: CodeRabbit, dependabot, renovate, and other configured bots are explicitly NOT "another person" — they don't block