Think First
- 2 installs
- Updated February 20, 2026
- ofershap/think-first
Enforces a read-then-plan-then-implement workflow so the agent understands existing code and proposes a plan before editing.
About
This skill changes agent behavior to read relevant files, understand root causes, check for existing code, and propose a plan before implementing changes. A developer uses it to reduce backtracking and wasted tokens on every task.
- Read before writing and propose a plan for 3+ file changes
- Minimal-change principle separating refactors from fixes
Think First by the numbers
- 2 all-time installs (skills.sh)
- Ranked #2,412 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ofershap/think-first --skill think-firstAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| Last updated | February 20, 2026 |
| Repository | ofershap/think-first ↗ |
What it does
Enforces a read-then-plan-then-implement workflow so the agent understands existing code and proposes a plan before editing.
Files
When to use
This skill is always active. It changes how the AI agent approaches every task - from "dive into code" to "understand first, plan second, implement third."
Critical Rules
1. Read Before Writing
Wrong: Immediately start editing files based on the user's request Correct: First read all relevant files, understand the existing code structure, patterns, and conventions
2. Understand the Full Picture
Wrong: Fix the symptom without understanding the root cause Correct: Trace the issue through the codebase - understand data flow, dependencies, and side effects
3. Check If It Already Exists
Wrong: Create a new utility function without checking if one exists Correct: Search the codebase for existing implementations before creating new ones
4. Propose a Plan for Complex Changes
Wrong: Start implementing a multi-file change without explaining the approach Correct: For changes touching 3+ files, outline the plan: what files change, what the approach is, what the risks are
5. Identify Affected Areas
Wrong: Make a change without considering what else it affects Correct: Before implementing, identify all files, tests, and features that could be affected
6. Consider Alternatives
Wrong: Implement the first approach that comes to mind Correct: For non-trivial changes, briefly consider 2-3 approaches and explain why you chose one
7. Verify Assumptions
Wrong: Assume a function exists or works a certain way Correct: Read the actual code to verify before building on assumptions
8. Minimal Change Principle
Wrong: Refactor everything while fixing a bug Correct: Make the smallest change that solves the problem - separate refactoring from bug fixes
9. Test Awareness
Wrong: Make changes without considering how to verify them Correct: Before implementing, identify how the change will be tested - existing tests, new tests, manual verification
10. Context Preservation
Wrong: Lose track of the original goal while exploring tangential issues Correct: Stay focused on the user's request - note tangential issues but don't chase them
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k