reasoning-protocol

Enforce structured DOING/EXPECT plans and AFTER reviews for tool calls.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/acrulopez/dotfiles --skill reasoning-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reasoning-protocol
Source: https://github.com/acrulopez/dotfiles/tree/main/.claude/skills/reasoning-protocol
Command: npx skills add https://github.com/acrulopez/dotfiles --skill reasoning-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit reasoning protocol that enforces structured thinking before and after every action, reducing errors and missteps during tool calls, file operations, code changes, and debugging.

Core Features & Use Cases

  • Before-action planning: outline DOING and EXPECT before performing actions to align expectations with outcomes.
  • After-action verification: compare RESULT and MATCHES to determine next steps and STOP conditions if unexpected.
  • Universal applicability: suitable for tool calls, file edits, debugging sessions, and any action with potential side effects.

Quick Start

Describe the action to be taken, predict the outcome, specify the next steps for both yes and no cases, then perform the action.

Frequently Asked Questions about reasoning-protocol

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

FAQPage Schema
How does structured thinking before tool calls prevent errors?

Structured thinking before tool calls prevents errors by requiring an explicit plan outlining what you are DOING and what you EXPECT, ensuring actions align with predicted outcomes before execution.

How do I implement a reasoning protocol for debugging?

To implement a reasoning protocol for debugging, outline your DOING, EXPECT, IF YES, and IF NO steps before acting, then perform an AFTER review checking RESULT, MATCHES, and THEREFORE conclusions to verify outcomes.

Can I use a reasoning protocol for file operations and code changes?

Yes, you can use a reasoning protocol for file operations and code changes. It is universally applicable to any action with potential side effects, requiring before-action planning and after-action verification to reduce missteps.

What is the best way to verify outcomes after an action with potential side effects?

The best way to verify outcomes after an action with potential side effects is conducting an AFTER review comparing the actual RESULT against expectations to determine MATCHES and define THEREFORE next steps or STOP conditions.

Why do I need to specify IF YES and IF NO conditions before performing an action?

You need to specify IF YES and IF NO conditions before performing an action to predefine next steps for both expected and unexpected outcomes, preventing impulsive decisions and reducing errors during tool calls or debugging.