agentleFS
Dianel555Dianel555/DSkills/skills/sequential-think/SKILL.md

sequential-think

Skill65 starsChanged 2 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run scripts/sequential_think_cli.py via Bash:

    line 13
  2. Very specific:

    Start with initial estimate of totalThoughts

    line 66
  3. Distinctive:

    Add more thoughts even after reaching initial end

    line 68
  4. Distinctive:

    Verify hypotheses based on chain-of-thought steps

    line 72
  5. Very specific:

    Only set nextThoughtNeeded: false when truly finished

    line 76
  6. Distinctive:

    Must have satisfactory, verified answer

    line 77
  7. Distinctive:

    Don't rush to conclusion

    line 78
  8. Very specific:

    Use branchFromThought to explore alternatives

    line 158
  9. Very specific:

    Only nextThoughtNeeded=false when truly done

    line 166
  10. Distinctive:

    Verify hypothesis before concluding

    line 167

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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:

# 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 [--format json|text]

# Clear thought history
python scripts/sequential_think_cli.py clear

Core Principles

Iterative Thinking Process

  • Each tool call = one "thought" in the chain
  • Build upon, question, or revise previous thoughts
  • Express uncertainty when it exists

Dynamic Thought Count

  • Start with initial estimate of totalThoughts
  • Adjust up/down as understanding evolves
  • Add more thoughts even after reaching initial end

Hypothesis-Driven Approach

  1. Generate hypotheses as potential solutions emerge
  2. Verify hypotheses based on chain-of-thought steps
  3. Repeat until satisfied with solution

Completion Criteria

  • Only set nextThoughtNeeded: false when truly finished
  • Must have satisfactory, verified answer
  • Don't rush to conclusion

When to Use

ScenarioUse Sequential Think
Complex debugging (3+ layers)✅ Yes
Architectural analysis✅ Yes
Multi-component investigation✅ Yes
Performance bottleneck analysis✅ Yes
Root cause analysis✅ Yes
Simple explanation❌ No
Single-file change❌ No
Straightforward fix❌ No

Parameters

ParameterTypeRequiredDescription
thoughtstringYesCurrent thinking step content
thoughtNumberintYesCurrent position in sequence (1-based)
totalThoughtsintYesEstimated total thoughts needed
nextThoughtNeededboolNoWhether more thinking needed (default: true)
isRevisionboolNoWhether this revises previous thinking
revisesThoughtintNoWhich thought number is being reconsidered
branchFromThoughtintNoBranching point thought number
branchIdstringNoIdentifier for current branch
needsMoreThoughtsboolNoSignal that more thoughts needed beyond estimate

Output Format

{
  "thoughtNumber": 3,
  "totalThoughts": 5,
  "nextThoughtNeeded": true,
  "branches": ["alt-approach"],
  "thoughtHistoryLength": 3
}

Workflow Pattern

Phase 1: Problem Decomposition

Thought 1: Identify problem scope and constraints
Thought 2: Break into sub-problems
Thought 3: Identify dependencies between sub-problems

Phase 2: Hypothesis Generation

Thought 4: Generate initial hypothesis
Thought 5: Identify evidence needed to verify

Phase 3: Verification & Iteration

Thought 6: Test hypothesis against evidence
Thought 7: Revise if needed (isRevision=true)
Thought 8: Branch if alternative path promising

Phase 4: Conclusion

Final Thought: Synthesize findings, provide answer (nextThoughtNeeded=false)

Best Practices

  1. Start with estimate, adjust as needed
    • Initial totalThoughts is just a guess
    • Increase if problem more complex than expected
    • Decrease if solution found early
  2. Use revisions for course correction
    • Mark isRevision=true when reconsidering
    • Reference revisesThought for clarity
  3. Branch for alternative approaches
    • Use branchFromThought to explore alternatives
    • Give meaningful branchId names
  4. Filter irrelevant information
    • Each thought should advance toward solution
    • Ignore tangential details
  5. Don't rush completion
    • Only nextThoughtNeeded=false when truly done
    • Verify hypothesis before concluding

Anti-Patterns

ProhibitedCorrect
Use for simple tasksReserve for complex multi-step problems
Skip thought numbersAlways increment correctly
Conclude without verificationVerify hypothesis before final thought
Ignore previous thoughtsBuild upon or explicitly revise
Fixed totalThoughtsAdjust as understanding evolves

Integration with Other Tools

With ACE-Tool

ACE-Tool → align current state → Sequential Think → analyze and plan

With Context7

Sequential Think → coordinate analysis → Context7 → provide official patterns

With Serena

Serena → symbol-level exploration → Sequential Think → systematic analysis

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.