Agent skill · Frontend

sequential-think

Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/analysis/sequential-think/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 Think Structured iterative thinking for complex problem-solving. Standalone CLI only (no MCP dependency). ## Execution Methods Run `scripts/sequential_think_cli.py` via Bash: ```bash # Process a thought python scripts/sequential_think_cli.py think \ --thought "First, let me analyze the problem structure..." \ --thought-number 1 \ --total-thoughts 5 # Continue thinking chain python scripts/sequential_think_cli.py think \ --thought "Based on step 1, I hypothesize that..." \ --thought-number 2 \ --total-thoughts 5 # Revise a previous thought python scripts/sequential_think_cli.py think \ --thought "Reconsidering step 1, I realize..." \ --thought-number 3 \ --total-thoughts 5 \ --is-revision \ --revises-thought 1 # Branch into alternative path python scripts/sequential_think_cli.py think \ --thought "Alternative approach: what if we..." \ --thought-number 4 \ --total-thoughts 6 \ --branch-from 2 \ --branch-id "alt-approach" # Final thought (complete chain) python scripts/sequential_think_cli.py think \ --thought "Conclusion: the solution is..." \ --thought-number 5 \ --total-thoughts 5 \ --no-next # View thought history python scripts/sequential_think_cli.py history [--for

What's inside
Steps it walks through
  1. Execution Methods
  2. Core Principles
  3. Iterative Thinking Process
  4. Dynamic Thought Count
  5. Hypothesis-Driven Approach
  6. Completion Criteria
  7. When to Use
  8. Parameters
  9. Output Format
  10. Workflow Pattern
  11. Phase 1: Problem Decomposition
  12. Phase 2: Hypothesis Generation
  13. Phase 3: Verification & Iteration
  14. Phase 4: Conclusion
Ships with 1 file
  • metadata.json
Commands it runs
Process a thought
python scripts/sequential_think_cli.py think \
Continue thinking chain
Revise a previous thought
Branch into alternative path
Final thought (complete chain)
View thought history
python scripts/sequential_think_cli.py history [--format json|text]
Clear thought history
python scripts/sequential_think_cli.py clear
More from claude-skill-registry
All skills →
About this skill
What does the sequential-think skill do?

Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill sequential-think --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