Esta skill debe usarse cuando el usuario pide \"pensemos esto a fondo\", \"analicemos paso a paso\", \"evaluemos opciones\", \"razonemos sobre esto\", \"pensemos detenidamente\", \"meditemos\", \"qué me sugieres\", \"qué me recomiendas\", \"esto es complejo\", \"esto es complicado\", \"problema grande\", o ante problemas que requieren análisis profundo, afectan múltiples componentes del sistema, tienen implicaciones arquitectónicas importantes, o representan decisiones de diseño con impacto significativo. IMPORTANTE: Invocar esta skill en lugar de usar seq-think MCP directamente - la skill proporciona workflow estructurado con generación de documentos de análisis.
View on GitHubplugins/dotclaudefiles/skills/deep-reason/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/DieGopherLT/dotclaudefiles/blob/main/plugins/dotclaudefiles/skills/deep-reason/SKILL.md -a claude-code --skill deep-reasonInstallation paths:
.claude/skills/deep-reason/To engage in deep, structured reasoning for complex problems, apply the sequential-thinking approach with these guidelines: ## Thought Process Guidelines During the sequential thinking process: ### 1. Initial Thoughts: Problem Space Definition - **Reduce scope** if the problem is too broad or unfocused - **Create the problem space**: Define the problem itself WITHOUT any influence from solutions or tools - See the problem as it truly is, not through the lens of potential solutions - Identify core constraints, requirements, and success criteria - Separate facts from assumptions ### 2. Solution Generation - Generate **multiple options or solutions** to the stated problem - Consider diverse approaches, not just the most obvious ones - Think creatively about different paths to the goal ### 3. Information Gathering - **Gather information** as needed throughout the thought process - Use tools (Read, Grep, Glob, WebFetch, MCPs, specialized agents, etc.) to understand: - The problem better - Existing code/patterns - Any proposed solutions - Technical constraints or documentation ### 4. Option Evaluation - **Evaluate each option** thoroughly, considering: - **Pros**: Benefits, strengths, advantages - **Cons**: Drawbacks, risks, limitations - Trade-offs between options - Implementation complexity - Long-term maintainability ### 5. Use Branches for Multiple Options - When thinking through **multiple distinct options or solutions**, use the **branch feature** of the MCP: - `branchFromThought`: Specify which thought number is the branching point - `branchId`: Give each branch a descriptive identifier (e.g., "option-redis", "option-inmemory") - This allows parallel exploration of different approaches ## After Completing the Thought Chain After completing the sequential thinking process and reaching a conclusion: 1. Present findings to the user concisely 2. Ask if they want a summary document using the `AskUserQuestion` tool: - Questio