sequential-thinking

Apply state-based reasoning with branch and revise thresholds for multi-step analysis.

13|2|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/petbrains/mvp-builder --skill sequential-thinking-petbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sequential-thinking
Source: https://github.com/petbrains/mvp-builder/tree/main/.claude/skills/sequential-thinking
Command: npx skills add https://github.com/petbrains/mvp-builder --skill sequential-thinking-petbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates unstructured, error-prone reasoning for complex problems by providing a framework for state-based analysis, branch/revise decision thresholds, and quality scoring that ensures thorough, logical solutions.

Core Features & Use Cases

  • State-Based Reasoning: Break down problems into explicit states, preconditions, effects, and verification steps.
  • Decision Framework: Clear rules for when to branch (confidence <60%), revise (fundamental error), or extend (incomplete analysis).
  • Use Case: Imagine debugging a complex race condition in distributed systems. This Skill guides you through systematic state analysis, identifies causal chains, and provides quality scoring to ensure your solution addresses root causes—not just symptoms.

Quick Start

Use the sequential-thinking skill to analyze and debug an intermittent API failure that occurs under high load but has no clear error messages.

Frequently Asked Questions about sequential-thinking

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

FAQPage Schema
How do I debug complex problems with multiple potential causes?

Sequential thinking breaks down multi-step problems into explicit states, preconditions, and causal chains. It applies decision rules—branch when confidence drops below 60%, revise on fundamental errors, or extend incomplete analysis—ensuring you systematically identify root causes rather than surface symptoms.

When should I use structured reasoning instead of trial-and-error debugging?

Use structured reasoning for problems with 3+ logical steps, multiple valid approaches, unclear root causes, or initial confidence below 70%. It's especially valuable for state transitions and causal chains where unstructured reasoning leads to incomplete or incorrect solutions.

How do I know when my analysis is thorough enough?

Sequential thinking includes quality scoring and convergence rules to verify solutions address root causes. The framework tells you when analysis is complete versus when you need to branch into alternatives or revise fundamental assumptions.

Can I use this approach for distributed systems debugging?

Yes. Sequential thinking guides systematic state analysis across system components, identifies causal chains in timing-dependent failures, and provides quality scoring to confirm solutions. It's effective for race conditions, intermittent failures, and high-load scenarios with unclear error messages.

What's the difference between branching and revising in problem-solving?

Branching explores alternative approaches when confidence is below 60%, keeping multiple paths open. Revising discards the current path when you identify a fundamental error in your reasoning, then restarts with corrected assumptions.