本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

agents

無料

List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

auto-loop

無料

TDD-based autonomous development loop with checkpoint recovery and observability changelog

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

changelog

無料

View and manage the runtime changelog for observability

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.

日本語の概要は準備中です。原文の説明を表示しています。

claude-world/director-mode-lite802026年8月31日 更新

claude-world のスキルをすべて見る

このスキルの問題を報告する