sequential-thinking

Decompose complex problems through iterative reasoning and structured revision.

9|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/duongdev/ccpm --skill sequential-thinking-duongdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sequential-thinking
Source: https://github.com/duongdev/ccpm/tree/main/skills/sequential-thinking
Command: npx skills add https://github.com/duongdev/ccpm --skill sequential-thinking-duongdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for tackling complex, multi-step problems, preventing overwhelm and ensuring thorough analysis. It guides you through iterative reasoning, dynamic scope adjustment, and explicit revision, leading to well-reasoned decisions and clear action plans.

Core Features & Use Cases

  • Problem Decomposition: Breaks down large challenges into manageable, logical steps, ideal for epic breakdown or architecture decisions.
  • Iterative Reasoning: Guides you through a thought process that adapts as new information emerges, allowing for revisions and branching.
  • Complexity Assessment: Helps identify all dimensions of complexity, assess risks, and provide concrete complexity ratings for tasks.
  • Use Case: When faced with a vague "Implement User Dashboard" epic, this skill will help you systematically break it down into layout, widget system, preferences, and data visualization components, identifying dependencies and estimating effort for each.

Quick Start

Break down the "User Dashboard" epic into manageable tasks.

Frequently Asked Questions about sequential-thinking

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

FAQPage Schema
How do I break down a complex project into manageable steps?

Problem decomposition breaks large projects into logical, sequenced tasks by assessing scope, identifying dependencies, and estimating effort for each component. This structured approach prevents overwhelm and surfaces hidden complexity in architecture decisions and epic planning.

What's the best way to approach root cause analysis?

Root cause analysis uses iterative reasoning and explicit techniques like the five-whys method to trace problems to their source. This skill guides you through systematic questioning and dynamic scope adjustment to identify underlying issues rather than symptoms.

How do I decide between different architecture approaches?

Architecture decision-making uses complexity assessment to evaluate multiple dimensions, identify risks, and rate effort for each option. The iterative reasoning process lets you revise assumptions as new information emerges and branch into alternatives.

Can I use this for planning when requirements are still unclear?

Yes. The skill explicitly handles uncertain scope through dynamic adjustment and revision mechanisms. As requirements clarify during planning, the framework adapts, allowing you to refine breakdowns and estimates without restarting.

How do I identify all the complexity in a task?

Complexity assessment maps multiple dimensions of a problem—technical, organizational, dependency-based—and provides concrete ratings for each. This prevents underestimation and reveals hidden effort in task breakdown and specification writing.