Focus problem

Skill claude-world/director-mode-lite/skills/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 codebase area.From its SKILL.md

Install

npx -y skills add claude-world/director-mode-lite --skill focus-problem

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in 382 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

Ask one question at a timein 73 of 1360
Write the spec using the templatein 22 of 1360
Ask clarifying questions if neededin 19 of 1360, across 18 files
Wait for user confirmation before proceedingin 19 of 1360
Save plans to the plans directoryin 17 of 1360, across 13 files
Check for product marketing context firstin 16 of 1360, across 5 files
Read the plan file completelyin 16 of 1360
Order tasks by dependencyin 16 of 1360
Gather context from the conversationin 15 of 1360, across 9 files
Explore the codebase instead of askingin 15 of 1360, across 13 files
Wait for explicit user approvalin 14 of 1360, across 13 files
Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

Scope the minimal solution
Choose the simplest viable option

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.