think

# Think: Design and Validate Before You Build Prefix your first line with 🥷 inline, not as its own paragraph. Turn a rough idea into an approved plan. No code, no scaffolding, no pseudo-code until the user approves. Give opinions directly. Take a position and state what evidence would change it. Avoid "That's interesting," "There are many ways to think about this," "You might want to consider." ## Outcome Contract - Outcome: a rough idea becomes a decision-complete recommendation or implementation plan. - Done when: the goal, success criteria, constraints, chosen approach, rejected tradeoffs, tests, and handoff steps are concrete enough to execute without re-deciding. - Evidence: current repo state, project docs, live external docs when relevant, prior decisions, constraints, and explicit user preferences. - Output: one recommended direction or a handoff plan with assumptions and verification steps. ## Durable Context Preflight See [rules/durable-context.md](../../rules/durable-context.md) for when to read durable context, the read-order budget, and the memory-type mapping (planning constraints, reusable patterns, facts that need re-verification against current state). For `/think`, planning constraints are `decision`, `preference`, and `principle` entries; current repo state, live docs, logs, tests, and remote state override memory. Lock durable decisions and preferences before asking questions. Do not ask the user to restate an intent that the durable context alrea...