Skip to content
Skills Library
Programming · Planning

focus-problem

/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.

Licence
MIT
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. Explore Codebase First
  2. Analysis Framework
  3. Output Template
Original SKILL.md headings · 88 lines, 316 words
SKILL.md preview
---
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:

Before dispatch, preserve the bounded exploration question and expected result.
If Claude's Agent tool is unavailable or withheld, or Codex's `spawn_agent`
interface is unavailable or withheld, the maximum depth is reached, or a
concurrency limit rejects the call, do not retry or invent exploration
findings. Return an incomplete `dispatch_request` and do not advance the plan.

Choose exactly one provider-native form:

- Claude Code: `Agent(subagent_type="Explore", model="haiku", prompt="<bounded prompt>")`
- Codex CLI: `spawn_agent(agent_type="explorer", task_name="focus_problem", message="<bounded prompt>")`

```markdown
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
""")
```

In Codex, send the same exploration request through `spawn_agent(...)`; do not
invoke the Claude example as a second dispatch.

## 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

```markdown
## 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.

Versions

The database has no other skills named focus-problem.

Database snapshot: 13.11.2026 · package version 87c0fd39aa5d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90explore-codebase
    Explore codebase files, patterns, and structure for a given topic. USE WHEN gathering implementation context before planning or executing tasks, when asked to research the codebase, or when a planning agent needs a Sub-Agent A (Codebase Research). Returns a Codebase Research…
  • 90explain-code
    Explain a piece of code using project knowledge and context. Use to understand unfamiliar code, get architecture context, learn patterns and gotchas, find similar implementations.
  • 100explore
    Multi-angle codebase exploration by parallel agents: structure, data flow, architecture, health. Use to map an unfamiliar repo. NOT for task research files (use create-research).
  • 90map-codebase
    Use when entering an unfamiliar codebase or area, before making non-trivial changes, when onboarding to a new system, or when planning a refactor that touches multiple modules. Activate for keywords like "explore", "map", "find where", "trace", "how does X work", "what calls Y",…
  • 90spec-explore
    Map a problem and understand the codebase before any change exists - ground every question in what the repo says, converge on an outcome, a scope, and an explicit not-in-scope boundary, then hand to `spec-propose`. Use when the user says "explore this", "/spec-explore", "help me…
  • 100plan
    Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.