vc:sequential-thinking
This Claude Code skill applies structured sequential thinking with dynamic adjustment for complex problem-solving. It enables users to decompose difficult problems into manageable thought steps, revise understanding as new insights emerge, explore alternative approaches through branching, and verify solutions through hypothesis testing. Use it when facing multi-step reasoning tasks with unclear scope, problems requiring course correction, or situations where maintaining context across interconnected analyses is critical.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-sequential-thinking && cp -r /tmp/vc-sequential-thinking/.claude/skills/vc-sequential-thinking ~/.claude/skills/vc-sequential-thinkingSKILL.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 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
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I''ll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I''ll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>
EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features/*/active/ only. Use after approach is decided.