Agent skill · Workflow & Productivity

sequential-thinking

Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing co

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill 0-sequential-thinking --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/analysis/0-sequential-thinking/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Sequential Thinking Structured problem-solving via manageable, reflective thought sequences with dynamic adjustment. ## When to Apply - Complex problem decomposition - Adaptive planning with revision capability - Analysis needing course correction - Problems with unclear/emerging scope - Multi-step solutions requiring context maintenance - Hypothesis-driven investigation/debugging ## Core Process ### 1. Start with Loose Estimate ``` Thought 1/5: [Initial analysis] ``` Adjust dynamically as understanding evolves. ### 2. Structure Each Thought - Build on previous context explicitly - Address one aspect per thought - State assumptions, uncertainties, realizations - Signal what next thought should address ### 3. Apply Dynamic Adjustment - **Expand**: More complexity discovered → increase total - **Contract**: Simpler than expected → decrease total - **Revise**: New insight invalidates previous → mark revision - **Branch**: Multiple approaches → explore alternatives ### 4. Use Revision When Needed ``` Thought 5/8 [REVISION of Thought 2]: [Corrected understanding] - Original: [What was stated] - Why revised: [New insight] - Impact: [What changes] ``` ### 5. Branch for Alternatives ```

What's inside
Steps it walks through
  1. When to Apply
  2. Core Process
  3. 1. Start with Loose Estimate
  4. 2. Structure Each Thought
  5. 3. Apply Dynamic Adjustment
  6. 4. Use Revision When Needed
  7. 5. Branch for Alternatives
  8. 6. Generate & Verify Hypotheses
  9. 7. Complete Only When Ready
  10. Application Modes
  11. Scripts (Optional)
  12. References
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the sequential-thinking skill do?

Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing co

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill 0-sequential-thinking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going