Agent skill · research science · secondsky

sequential-thinking

Systematic step-by-step reasoning with revision and branching. Use for complex problems, multi-stage analysis, design planning, problem decomposition, or encountering unclear scope, alternative approaches needed, revision requirements.

Why this skill is useful

Provides a structured approach to complex problem-solving that the AI wouldn't reliably generate on its own.

What it needs

About 2k tokens when loaded. Last updated 2026-08-06. 204 stars on the source repository.

What this skill does

Sequential Thinking Enables structured problem-solving through iterative reasoning with revision and branching capabilities. Core Capabilities Iterative reasoning: Break complex problems into sequential thought steps Dynamic scope: Adjust total thought count as understanding evolves Revision tracking: Reconsider and modify previous conclusions Branch exploration: Explore alternative reasoning paths from any point Maintained context: Keep track of reasoning chain throughout analysis When to Use Use mcpreasoningsequentialthinking when: Problem requires multiple interconnected reasoning steps Initial scope or approach is uncertain Need to filter through complexity to find core issues May need to backtrack or revise earlier conclusions Want to explore alternative solution paths Don't use for: Simple queries, direct facts, or single-step tasks. Basic Usage The MCP tool mcpreasoningsequentialthinking accepts these parameters: Required Parameters thought (string): Current reasoning step nextThoughtNeeded (boolean): Whether more reasoning is needed thoughtNumber (integer): Current step number (starts at 1) totalThoughts (integer): Estimated total steps needed Optional Parameters isRevision (boolean): Indicates this revises previous thinking revisesThought (integer): Which thought number is being reconsidered branchFromThought (integer): Thought number to branch from branchId (string): Identifier for this reasoning branch Workflow Pattern Simple Example Advanced Features Revision Pattern When you realize an earlier conclusion was wrong: Branching Pattern When exploring alternative approaches: Tips Start with rough estimate for totalThoughts, refine as you progress Use revision when assumptions prove incorrect Branch when multiple approaches seem viable Express uncertainty explicitly in thoughts Adjust scope freely - accuracy matters less than progress visibility

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills secondsky/sequential-thinking

View the source on GitHub

Browse the @skills marketplace