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.
Enables structured problem-solving through iterative reasoning with revision and branching capabilities.
/plugin marketplace add GGPrompts/TabzBeads/plugin install tools@tabz-beadsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/advanced.mdreferences/examples.mdEnables structured problem-solving through iterative reasoning with revision and branching capabilities.
Use mcp__reasoning__sequentialthinking when:
Don't use for: Simple queries, direct facts, or single-step tasks.
The MCP tool mcp__reasoning__sequentialthinking accepts these parameters:
thought (string): Current reasoning stepnextThoughtNeeded (boolean): Whether more reasoning is neededthoughtNumber (integer): Current step number (starts at 1)totalThoughts (integer): Estimated total steps neededisRevision (boolean): Indicates this revises previous thinkingrevisesThought (integer): Which thought number is being reconsideredbranchFromThought (integer): Thought number to branch frombranchId (string): Identifier for this reasoning branch1. Start with initial thought (thoughtNumber: 1)
2. For each step:
- Express current reasoning in `thought`
- Estimate remaining work via `totalThoughts` (adjust dynamically)
- Set `nextThoughtNeeded: true` to continue
3. When reaching conclusion, set `nextThoughtNeeded: false`
// First thought
{
thought: "Problem involves optimizing database queries. Need to identify bottlenecks first.",
thoughtNumber: 1,
totalThoughts: 5,
nextThoughtNeeded: true
}
// Second thought
{
thought: "Analyzing query patterns reveals N+1 problem in user fetches.",
thoughtNumber: 2,
totalThoughts: 6, // Adjusted scope
nextThoughtNeeded: true
}
// ... continue until done
For revision patterns, branching strategies, and complex workflows, see:
totalThoughts, refine as you progressThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.