Skip to main content

sequential-thinking

Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.

설치로 이동

소스 정보

저장소
LongLeo287/SEOSONA-OS
최근 소스 활동
2026년 8월 4일 05:01
감지된 SKILL.md 언어
영어
스타
2
포크
1

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
15 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
sequential-thinking
description
Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.
argument-hint
[problem to analyze step-by-step]
license
MIT
metadata
{"author":"claudekit","version":"1.0.0"}
# Sequential Thinking Structured problem-solving via manageable, reflective thought sequences with dynamic adjustment. ## When to Apply - Complex problem decomposition - Adaptive planning with revision capability - Analysis needing course correction - Problems with unclear/emerging scope - Multi-step solutions requiring context maintenance - Hypothesis-driven investigation/debugging ## Core Process ### 1. Start with Loose Estimate ``` Thought 1/5: [Initial analysis] ``` Adjust dynamically as understanding evolves. ### 2. Structure Each Thought - Build on previous context explicitly - Address one aspect per thought - State assumptions, uncertainties, realizations - Signal what next thought should address ### 3. Apply Dynamic Adjustment - **Expand**: More complexity discovered → increase total - **Contract**: Simpler than expected → decrease total - **Revise**: New insight invalidates previous → mark revision - **Branch**: Multiple approaches → explore alternatives ### 4. Use Revision When Needed ``` Thought 5/8 [REVISION of Thought 2]: [Corrected understanding] - Original: [What was stated] - Why revised: [New insight] - Impact: [What changes] ``` ### 5. Branch for Alternatives ``` Thought 4/7 [BRANCH A from Thought 2]: [Approach A] Thought 4/7 [BRANCH B from Thought 2]: [Approach B] ``` Compare explicitly, converge with decision rationale. ### 6. Generate & Verify Hypotheses ``` Thought 6/9 [HYPOTHESIS]: [Proposed solution] Thought 7/9 [VERIFICATION]: [Test results] ``` Iterate until hypothesis verified. ### 7. Complete Only When Ready Mark final: `Thought N/N [FINAL]` Complete when: - Solution verified - All critical aspects addressed - Confidence achieved - No outstanding uncertainties ## Application Modes **Explicit**: Use visible thought markers when complexity warrants visible reasoning or user requests breakdown. **Implicit**: Apply methodology internally for routine problem-solving where thinking aids accuracy without cluttering response. ## Scripts (Optional) Optional scripts for deterministic validation/tracking: - `scripts/process-thought.js` - Validate & track thoughts with history - `scripts/format-thought.js` - Format for display (box/markdown/simple) See README.md for usage examples. Use when validation/persistence needed; otherwise apply methodology directly. ## References Load when deeper understanding needed: - `references/core-patterns.md` - Revision & branching patterns - `references/examples-api.md` - API design example - `references/examples-debug.md` - Debugging example - `references/examples-architecture.md` - Architecture decision example - `references/advanced-techniques.md` - Spiral refinement, hypothesis testing, convergence - `references/advanced-strategies.md` - Uncertainty, revision cascades, meta-thinking
GitHub에서 보기