sequential-thinking
From the author
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Install
npx skills add Microck/ordinary-claude-skills --skill sequential-thinking -a claude-code
Installs to .claude/skills/sequential-thinking/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- brainstormingnexu-io/open-designTransform rough ideas into fully-formed designs through structured questioning and alternative exploration. Useful early in concept work.Planning★ 103.5K
- thinkAgriciDaniel/claude-obsidianApply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.Planning★ 15.7K
- planhashgraph-online/awesome-codex-pluginsShape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.Planning★ 1.4K
- designhashgraph-online/awesome-codex-pluginsUse for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.Design★ 1.4K
- process-designcbrock84/headcountDesigns, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.Design★ 2.1K
- architectaiskillstore/marketplaceDesign systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.Planning★ 443
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in