focus-problem
Use Cautionnpx machina-cli add skill claude-world/director-mode-lite/focus-problem --openclawFocus Problem Analysis
Analyze: $ARGUMENTS
Explore Codebase First
Before diving in, use the Explore agent to understand the context:
Task(subagent_type="Explore", model="haiku", prompt="""
Explore the codebase for: $ARGUMENTS (thoroughness: medium)
Focus on:
1. Relevant files and modules
2. Existing similar features
3. Test patterns
4. Architecture patterns
""")
Analysis Framework
1. Core Problem Identification
- What is the real problem?
- Why does it need to be solved?
- What happens if we don't solve it?
2. Minimal Solution Scope
- What's the minimum change needed?
- Which features are essential?
- What can be deferred or omitted?
3. Solution Evaluation
- Option A (Simplest):
- Option B (Balanced):
- Option C (Complete):
- Recommendation: Choose the simplest viable option
4. Implementation Plan
- Step 1: Write tests
- Step 2: Minimal implementation
- Step 3: Update documentation
- Step 4: Commit changes
Output Template
## Problem Definition
### Summary
[One sentence description]
### User Need
[Who needs this? What do they want to achieve?]
### Success Criteria
[How do we know it's done?]
### Scope
- In scope: [List]
- Out of scope: [List]
### Affected Files
- [file1.ts] - [why]
- [file2.ts] - [why]
### Risk Assessment
- [Potential risks and mitigations]
Follow this process strictly. Don't skip steps.
Source
git clone https://github.com/claude-world/director-mode-lite/blob/main/skills/focus-problem/SKILL.mdView on GitHub Overview
focus-problem guides you through rigorous problem analysis by first using the Explore agent to inspect the codebase context for ARGUMENTS. It then applies a structured framework to identify the real problem, define a minimal solution, compare options, and outline an actionable implementation plan. The approach helps teams avoid scope creep and align stakeholders on a clear path forward.
How This Skill Works
First, it runs an Explore subagent to gather codebase context: relevant files, existing features, tests, and architecture patterns. Then it applies a four-part framework (problem definition, minimal scope, evaluation of options, and an implementation plan) and outputs a problem definition and plan in a standard Markdown template.
When to Use It
- When starting work on a bug or feature with unclear scope
- When a decision requires understanding codebase context and dependencies
- When you need to minimize changes by identifying a minimal viable solution
- When evaluating trade-offs among simple, balanced, and complete options
- When documenting implementation steps and risk assessment before coding
Quick Start
- Step 1: Define ARGUMENTS for the problem you want to analyze
- Step 2: Run the Explore agent to map codebase context (files, features, tests, architecture)
- Step 3: Apply the Analysis Framework and generate the Output Template plus an Implementation Plan
Best Practices
- Clearly define ARGUMENTS before analysis
- Run Explore early to surface context (files, tests, patterns)
- Follow the four-stage framework: Problem, Scope, Evaluation, Plan
- Favor the simplest viable option with measurable success criteria
- Capture a detailed Output Template including affected files and risks
Example Use Cases
- Debugging a failing login flow by analyzing root cause and proposing a minimal fix
- Evaluating a new search feature by analyzing codebase and identifying scope
- Refactoring a monolith module; assessing risks and minimal changes
- Adding regression tests after exploring test patterns and coverage gaps
- Assessing migration to a new architecture by mapping architecture patterns
