Analyze technical decisions through a structured 3-stage thinking workflow.
npx skills add https://github.com/HMWKR/claude-code-skills --skill think-deep
Please help me install this Agent Skill. Skill: think-deep Source: https://github.com/HMWKR/claude-code-skills/tree/main/skills/think-deep Command: npx skills add https://github.com/HMWKR/claude-code-skills --skill think-deep
This Skill eliminates the risk of inconsistent analytical depth for important technical and design decisions, avoiding both superficial thinking that misses critical risks and unnecessarily token-heavy full deep dives when a balanced, structured approach is sufficient.
Use the think-deep skill to analyze the proposed microservice architecture for the payment processing system and identify potential risks, hidden assumptions, and optimization opportunities.
High-intent search queries and answers about installing and using this skill.
To plan a refactoring strategy without missing risks, use a 3-stage structured thinking workflow that classifies context, deconstructs assumptions, and applies adaptive execution loops to validate outcomes.
The best way to analyze microservice architecture for hidden assumptions is applying a fused pipeline of complementary thinking skills with mandatory stage bridge confirmations to ensure alignment and avoid premature conclusions.
Structured thinking improves high-stakes technology selection by enforcing balanced analytical depth that avoids superficial thinking while preventing unnecessarily token-heavy maximum-depth dives.
Yes, you need mandatory stage bridge confirmations for architecture design decisions to ensure explicit user approval before progressing between stages, preventing premature conclusions and maintaining alignment.
You should avoid maximum-depth thinking for technical strategy planning when a balanced, structured approach is sufficient, preventing unnecessarily token-heavy workflows while still rigorously validating actionable outcomes.
Yes, you can use adaptive OODA execution loops for option optimization within the deep analysis stage to ensure technical decisions are validated and produce actionable outcomes.
kokuyouwindDefine a standard PR description format with What/Why/How structure.
distribucionesfayosmoreno-sysAnalyze and prioritize technical debt in software codebases.
purvishrivastava27Conduct multi-source research and produce structured analytical reports.
amadeus-dlcRun the isolated AI-DLC practices-discovery stage without advancing the main workflow.
