sequential-plan

arinbalyan 的头像作者 arinbalyan

Use sequential thinking MCP for comprehensive problem planning

📖 中文导读:Use sequential thinking MCP for comprehensive problem planning 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: sequential-plan description: Use sequential thinking MCP for comprehensive problem planning license: MIT compatibility: opencode metadata: workflow: planning priority: high

Sequential Planning

This skill guides using the sequentialthinking MCP for complex problem solving.

What I Do

  1. Break down complex problems
  2. Use sequential thinking for step-by-step analysis
  3. Generate hypotheses and verify them
  4. Create actionable plans
  5. Document the reasoning process

When To Use Me

Use this skill when:

  • Tackling complex features
  • Debugging difficult issues
  • Making architectural decisions
  • Planning refactoring work
  • Analyzing system design

Sequential Thinking Process

Phase 1: Problem Definition

Thought 1: Define the problem clearly
- What is the actual requirement?
- What are the constraints?
- What's the expected outcome?

Phase 2: Analysis

Thoughts 2-4: Break down into components
- Identify sub-problems
- Find dependencies
- Assess complexity

Phase 3: Hypothesis

Thoughts 5-6: Generate solution hypotheses
- Propose approaches
- Consider alternatives
- Evaluate trade-offs

Phase 4: Verification

Thoughts 7-8: Verify and refine
- Check assumptions
- Validate approach
- Revise if needed

Phase 5: Plan

Final thoughts: Create actionable plan
- Step-by-step tasks
- Order of implementation
- Risk mitigation

Example Usage

// Using sequentialthinking MCP
await mcp.sequentialthinking({
  thought: "Define: User wants authentication system",
  thoughtNumber: 1,
  totalThoughts: 8,
  nextThoughtNeeded: true
})

await mcp.sequentialthinking({
  thought: "Break down: Need login, register, JWT, password reset",
  thoughtNumber: 2,
  totalThoughts: 8,
  nextThoughtNeeded: true
})

// Continue through all phases...

Tips

  • Adjust totalThoughts based on complexity
  • Use isRevision when backtracking
  • Don't rush - thinking saves implementation time
  • Document key decisions from the process
  • Store important conclusions in memory MCP