think-full

Enforce a 6-step sequential thinking workflow for strategic decisions.

Updated May 6, 2026
One-click install
npx skills add https://github.com/HMWKR/claude-code-skills --skill think-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think-full
Source: https://github.com/HMWKR/claude-code-skills/tree/main/skills/think-full
Command: npx skills add https://github.com/HMWKR/claude-code-skills --skill think-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users risk costly oversights when making high-stakes decisions like technical architecture design or business strategy formulation by relying on incomplete, single-angle reasoning that misses critical assumptions and edge cases.

Core Features & Use Cases

  • Mandatory 6-Step Sequential Pipeline: Runs Cynefin problem classification, purpose clarification, first principles assumption validation, prompt optimization, deep expert analysis, and adaptive OODA execution in fixed order with handoff objects between each stage to ensure no steps are skipped.
  • Built-in Guardrails: Includes mandatory user confirmation between stages, backward navigation for earlier stage revisions, and a fast mode for compressed confirmations when time is limited.
  • Use Case: For example, when planning a migration from a monolithic to microservice architecture, this skill ensures you first classify the problem complexity, validate core technical assumptions, optimize your approach, and create an adaptive execution plan instead of jumping straight to implementation.

Quick Start

Use the think-full skill to analyze our planned migration from monolithic to microservice architecture, including risk assessment and implementation roadmap.

Frequently Asked Questions about think-full

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is deep reasoning for high-stakes strategic decisions and when do I need it?

Deep reasoning for critical decisions enforces a 6-step sequential thinking workflow to eliminate incomplete analysis. You need it for major architecture design or technology stack selection to ensure multi-angle validation of assumptions and constraints before implementation.

How do I validate assumptions and plan a microservice architecture migration?

To validate assumptions for a microservice architecture migration, you must sequentially execute problem classification, root purpose identification, and first principles assumption validation. This ensures you assess risks and create an adaptive OODA execution plan rather than jumping straight to implementation.

Can I use a sequential thinking workflow for complex technology stack selection?

Yes, you can use a sequential thinking workflow for complex technology stack selection. It applies Cynefin problem classification and deep expert analysis to validate technical constraints and optimize your strategic decisions through a structured, multi-stage pipeline with mandatory user confirmation.

What is the best way to structure architectural design analysis to avoid costly oversights?

The best way to structure architectural design analysis is a fixed 6-step pipeline running from problem classification to adaptive execution planning. This approach uses handoff objects between stages and built-in guardrails to ensure no steps are skipped, preventing single-angle reasoning oversights.

Does the deep reasoning workflow allow backward navigation to revise earlier analysis stages?

Yes, the deep reasoning workflow allows backward navigation to revise earlier analysis stages. It includes built-in guardrails for mandatory user confirmation between stages and offers a fast mode for compressed confirmations, ensuring flexibility without skipping the sequential validation process.