ck:sequential-thinking
Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.
- License 许可
- MIT
- 最近更新
- 2026-05-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ck:sequential-thinking
- license
- MIT
- version
- 1.0.0
- description
- Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.
- argument-hint
- [problem to analyze step-by-step]
02 资源文件 14
- 其他.env.example308 B
- 其他.gitignore180 B
- 参考文档package.json697 B
- 参考文档README.md5.4 KB
- 参考文档references/advanced-strategies.md2.5 KB
- 参考文档references/advanced-techniques.md2.3 KB
- 参考文档references/core-patterns.md2.5 KB
- 参考文档references/examples-api.md2.2 KB
- 参考文档references/examples-architecture.md2.6 KB
- 参考文档references/examples-debug.md2.4 KB
- 脚本scripts/format-thought.js4.7 KB
- 脚本scripts/process-thought.js6.6 KB
- 脚本tests/format-thought.test.js3.6 KB
- 脚本tests/process-thought.test.js5.6 KB
03 SKILL.md 正文
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 historyscripts/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 patternsreferences/examples-api.md- API design examplereferences/examples-debug.md- Debugging examplereferences/examples-architecture.md- Architecture decision examplereferences/advanced-techniques.md- Spiral refinement, hypothesis testing, convergencereferences/advanced-strategies.md- Uncertainty, revision cascades, meta-thinking
04 同仓库更多 Skills
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:research
Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.
plann
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
ck:databases
Design schemas, write queries for MongoDB and PostgreSQL. Use for database design, SQL/NoSQL queries, aggregation pipelines, indexes, migrations, replication, performance optimization, psql CLI.
ck:brainstorm
Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.
ck:backend-development
Build backends with Node.js, Python, Go (NestJS, FastAPI, Django). Use for REST/GraphQL/gRPC APIs, auth (OAuth, JWT), databases, microservices, security (OWASP), Docker/K8s.