sequential-think
SolidMulti-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.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- Dianel555
- Repository
- Dianel555/DSkills
- Created
- 7 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
sequential-thinking
Dynamic, reflective step-by-step problem solving and hypothesis refinement
sequential-thinking
Structured reasoning harness for problems where shallow thinking fails or hallucination is costly. Use whenever a question requires multi-step reasoning, involves competing hypotheses, has multiple interacting components, or carries irreversible consequences. Activate for debugging with unclear root causes, intermittent or multi-component issues, incident post-mortems, choosing between multiple valid approaches, architecture or design tradeoffs, causal chain analysis, high-stakes decisions, and any task where the first plausible answer is suspiciously easy. Provides reasoning modes (abductive, counterfactual, first-principles, inversion, and more), grounding techniques against confabulation, adversarial self-checks, root-cause playbooks, and automatic multi-approach synthesis (independent angles run in parallel and compared) — all through the `mcp__sequential-thinking__sequentialthinking` tool. Skip for trivial lookups, obvious fixes, and single-step questions.
sequential-thinking
Use the Sequential Thinking MCP tool effectively for complex, multi-step problems. Triggers when: planning multi-phase implementations, debugging with uncertain root cause, exploring design alternatives, breaking down ambiguous requirements, or any task where the full scope isn't clear upfront. Teaches revision, branching, and dynamic thought extension (needsMoreThoughts) to avoid linear-only usage patterns.