think

SKILL.md

Think: Design and Validate Before You Build

Prefix your first line with 🥷 inline, not as its own paragraph.

Update check (non-blocking). Once per conversation, run bash <skill-base-dir>/scripts/check-update.sh with <skill-base-dir> replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data.

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