thinking-tools

name	thinking-tools
description	Structured thinking patterns for agent self-reflection. Includes think-about-collected-information (validate research), think-about-task-adherence (stay on track), and think-about-whether-you-are-done (completion validation).
version	1.0.0
model	sonnet
invoked_by	agent
user_invocable	false
tools	["Read","Glob","Grep"]
best_practices	["Use think-about-collected-information after research/exploration phases","Use think-about-task-adherence before making code changes","Use think-about-whether-you-are-done before declaring completion","Be honest in self-assessment, don't skip steps to appear fast","Document gaps found during reflection"]
error_handling	graceful
streaming	supported
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	79e68d7eac252167

Structured Thinking Framework - Self-reflection patterns for quality agent work. - Validating completeness of collected information - Ensuring adherence to the original task - Confirming work is truly complete before stopping - Identifying gaps in understanding or implementation - Preventing scope creep and tangential work

Overview

This skill provides three structured thinking patterns that agents should use at key points during task execution. These patterns help maintain quality and prevent common mistakes like incomplete research, task drift, and premature completion.

Thinking Pattern 1: Think About Collected Information

When to Use: After completing a non-trivial sequence of searching steps like:

• Reading multiple files
• Searching for symbols or patterns
• Exploring directory structures
• Gathering requirements

Self-Assessment Questions:

## Information Completeness Check

1. **Sufficiency**: Do I have enough information to proceed?
   - [ ] I understand the relevant code structure
   - [ ] I know the dependencies and relationships
   - [ ] I have identified all affected components

2. **Relevance**: Is all collected information relevant?
   - [ ] Information directly relates to the task
   - [ ] No tangential exploration
   - [ ] Focused on actionable insights

3. **Gaps**: What am I missing?
   - [ ] Are there files I should read but haven't?
   - [ ] Are there patterns I should search for?
   - [ ] Do I need to understand related systems?

4. **Confidence**: How confident am I in my understanding?
   - [ ] High: Ready to proceed
   - [ ] Medium: Minor clarification needed
   - [ ] Low: More research required

**Decision**: [Proceed / Gather More Information / Ask User]

Example Reflection:

I've read the authentication module (auth.ts) and the user model (user.ts).
I understand how login works but I haven't checked:
- How session tokens are managed
- Where logout is implemented
- What the error handling pattern is

Decision: Read session.ts and error-handler.ts before proceeding.

**Scenario**: Agent is asked to "fix the broken search feature" **Related Skills**: - `verification-before-completion` - Complements completion validation - `tdd` - Test-driven development integrates with completion checks - `sequential-thinking` - Structured problem decomposition