think-better

Generates a structured pre-task opener with goal, premortem, verifier, and routing before tool calls.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/raian-pollock/operator-skills --skill think-better-raian-pollock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: think-better
Source: https://github.com/raian-pollock/operator-skills/tree/main/think-better
Command: npx skills add https://github.com/raian-pollock/operator-skills --skill think-better-raian-pollock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often dive into non-trivial tasks without externalizing the goal, success criterion, or likely failure mode, leading to wasted tokens, silent wrong assumptions, and work committed to the wrong branch. This Skill enforces a short, evidence-backed thinking opener before any tool calls. ## Core Features & Use Cases - Six-line structured opener: goal with decision criterion, ordered approach bullets, scope with unverified assumptions, one-line premortem, named verifier, and branch/worktree routing decision. - Auto-trigger rules: fires on tasks with 2+ tool calls, decisions under uncertainty, research or audit work, and cross-file edits, while explicitly skipping mechanical one-line fixes and QA runs. - Inferential check for strategic tasks: tags load-bearing claims by evidence level, names biases to guard against, and requires a one-line falsifier on quantitative or causal reasoning. - Use Case: Before refactoring across multiple files, the agent writes the opener first, catching an unstated assumption about scope with a quick grep and confirming the correct target branch before any code touches disk. ## Quick Start Ask the agent to plan a non-trivial task and it will write the six-line think-better opener covering goal, approach, scope, premortem, verifier, and routing before making any tool calls.

Frequently Asked Questions about think-better

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent plan before acting on a task?▼

Load this Skill so the agent writes a six-line opener before tool calls: goal with a done criterion, 2-3 approach bullets, scope with unverified assumptions, a one-line premortem, a verifier, and a branch routing decision. It triggers automatically on non-trivial tasks.

What is a premortem for AI agent tasks?▼

A premortem is a single line written before execution: "If this comes back wrong, most likely reason: ___." Based on Klein's HBR research, it forces the agent to name the most probable failure mode before spending tokens, catching misframings early.

When should the structured opener be skipped?▼

Skip it on single-file mechanical edits like renames, formatting, or typos, bug fixes with clear repro steps from the user, tasks already inside a project's own planning-mode process, and QA-only verification runs.

Can I use this planning discipline outside Claude Code?▼

Yes. The package includes think-better-portable.md, a condensed four-line version you can paste into ChatGPT custom instructions, an AGENTS.md file, or any system-prompt-driven agent runtime.

Why does the skill reject frameworks like PDCA, 5 Whys, and OODA?▼

The documentation classifies them as vocabulary cargo cults: their original mechanisms rely on statistical loops over physical processes and do not transfer to single LLM tasks. Only premortem, plan-then-execute, and external verifiers survived the evidence review.