/focus-problem
Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar
$ npx -y skills add claude-world/director-mode-lite --skill focus-problem --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/focus-problem
Context preview
The summary Claude sees to decide when to auto-load this skill.
Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar
SKILL.md
focus-problem.SKILL.mdname: focus-problem
description: "Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar codebase area."
user-invocable: true
Focus Problem Analysis
Analyze: $ARGUMENTS
Explore Codebase First
Before diving in, use the Explore agent to understand the context:
Agent(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.
Read more
name: focus-problem description: "Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar codebase area." user-invocable: true
Focus Problem Analysis
Analyze: $ARGUMENTS
Explore Codebase First
Before diving in, use the Explore agent to understand the context:
Agent(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.
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
Other skills on director-mode-lite.
- /changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Open skill - /agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
Open skill - /agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
Open skill - /agents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
Open skill - /auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog
Open skill - /changelog
View and manage the runtime changelog for observability
Open skill

