sequential-thinking

Structure multi-step reasoning with numbered steps, revision checkpoints, and branch exploration.

310|45|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Mathews-Tom/praxis-skills --skill sequential-thinking-mathews-tom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sequential-thinking
Source: https://github.com/Mathews-Tom/praxis-skills/tree/main/skills/sequential-thinking
Command: npx skills add https://github.com/Mathews-Tom/praxis-skills --skill sequential-thinking-mathews-tom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an explicit, repeatable methodology for multi-step reasoning so models and users can produce verifiable intermediate results, handle branching and revisions, and avoid silent or circular reasoning. It replaces a legacy MCP tool by encoding step numbering, revision checkpoints, branch exploration, dynamic scope updates, and final verification into plain prompting.

Core Features & Use Cases

  • Numbered Step Execution: Work through 3–10+ numbered thoughts with a clear sub-goal, reasoning, and intermediate conclusion for each step.
  • Revision Checkpoints: Mandatory self-checks every few steps with explicit "Revising Step N" markers to correct prior conclusions and list downstream impacts.
  • Branch Exploration: Visible fork points with labeled approaches, short comparative evaluation, and a commitment rationale; briefly explore alternatives when consequential.
  • Dynamic Scope Adjustment & Verification: Update estimated step counts mid-analysis and conclude with a verification checklist that traces requirements to specific steps.
  • Use Cases: Deep debugging sessions, architectural decision-making, formal proofs, and any analysis needing stepwise traceability and error-correction.

Quick Start

Apply the sequential-thinking protocol to diagnose intermittent service failures by decomposing the problem into numbered steps, running periodic revision checkpoints, exploring up to two branches when necessary, and finishing with a verification checklist.

Frequently Asked Questions about sequential-thinking

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

FAQPage Schema
How do I structure chain-of-thought reasoning for complex debugging?

Chain-of-thought reasoning for debugging is structured by decomposing problems into 3–10+ numbered steps, each with a sub-goal, reasoning, and intermediate conclusion. Periodic revision checkpoints enable explicit error correction and downstream impact analysis.

What is stepwise reasoning for architectural decision-making?

Stepwise reasoning for architectural decision-making is a methodology that uses explicit step decomposition, branch exploration with comparative evaluation, and a final verification checklist to avoid silent or circular conclusions. It provides repeatable, verifiable intermediate results.

How do I explore alternative branches during multi-step problem solving?

You explore alternative branches by creating visible fork points with labeled approaches, performing a short comparative evaluation, and documenting a commitment rationale. This ensures consequential alternatives are briefly explored before continuing the main analysis.

How do I verify formal proofs without external tools?

You verify formal proofs without external tools by concluding the analysis with a mandatory verification checklist. This checklist traces specific requirements back to individual numbered steps, ensuring all constraints are met through pure prompting.

When should I not use sequential step decomposition for analysis?

You should avoid sequential step decomposition for simple, single-step tasks that do not require traceability or error correction. It is designed for complex analyses needing dynamic scope updates, branch labeling, and revision checkpoints.