ry-run/run-skills · Archived

sequential-thinking

Use Sequential Thinking MCP for explicit reasoning steps with revisions, branching, and uncertainty handling. Use it when the main need is to structure analysis, planning, or decision-making, rather than manage a persistent task system.

First seen May 6, 2026

Installation

$ npx skills add ry-run/run-skills --skill sequential-thinking

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ry-run/run-skills · top by installs.

npx skills add ry-run/run-skills

Browse all from ry-run/run-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,517 B
  • docs SUMMARY.md 263 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Sequential Thinking

Quick start

Goal: externalize a long reasoning chain when the problem is ambiguous, multi-stage, or likely to need course correction.

Primary entry point:

  • mcp__sequential_thinking__sequentialthinking

Reference notes: skills/sequential-thinking/references/sequential-thinking.md

When to use it

  • Complex debugging with multiple hypotheses.
  • Planning or design with tradeoffs.
  • Problems where you may need to revise earlier assumptions.
  • Multi-step analysis where the answer is not obvious upfront.

When not to use it

  • Simple factual lookups.
  • Straightforward code edits with already-clear scope.
  • Cases where direct execution is faster than explicit deliberation.

Workflow

  1. Start with an estimated totalThoughts.
  2. Record each step with increasing thoughtNumber.
  3. Mark revisions or branches when you change course.
  4. Stop only when the solution is actually stable.

Guardrails

  • Keep thoughts decision-oriented, not verbose for its own sake.
  • Revise earlier thoughts when evidence changes.
  • Do not use it as a substitute for gathering facts from code or tools.

References

  • Condensed notes: skills/sequential-thinking/references/sequential-thinking.md