issue-size-estimation
Defines standards for issue sizing and splitting tasks to keep development units under 200 lines.
Install
mkdir -p .claude/skills/issue-size-estimation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14376" && unzip -o skill.zip -d .claude/skills/issue-size-estimation && rm skill.zipInstalls to .claude/skills/issue-size-estimation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Issue粒度判定とコード行数見積もりの基準、サイズラベル、分割判定ロジックを定義Key capabilities
- →Estimate code lines for implementation tasks
- →Categorize issues by size (xs, s, m, l, xl)
- →Determine if an issue needs decomposition
- →Estimate lines based on issue labels
- →Estimate lines based on keywords in title/body
How it works
The skill estimates code lines and determines issue size by prioritizing existing labels, then design document code blocks, and finally keyword analysis from the issue title and body.
Inputs & outputs
When to use issue-size-estimation
- →Estimate code size
- →Split large issue
- →Apply size labels
About this skill
Issue粒度判定 & コード行数見積もり
参照元: 実装ワークフローの粒度判定ロジック
概要
実装タスクは200行以下のIssueを対象とすることを推奨する。
大きなIssueは事前に /decompose-issue で分解してから実行すること。
粒度判定基準
| 粒度 | 対応 |
|---|---|
| 200行以下 | 直接実装可能 |
| 200行超 | /decompose-issue で分割してから実装 |
| 新規設計 | /detailed-design-workflow で設計時に適切な粒度でIssue作成 |
粒度ルール
| 項目 | 基準 |
|---|---|
| コード量 | 200行以下 |
| ファイル数 | 1-3ファイル |
| 責務 | 単一責務（1つの機能・1つの目的） |
| テスト可能性 | 独立してテスト可能 |
| 所要時間目安 | 10-15分で実装完了 |
サイズラベル
プロジェクトで以下のラベルを使用することを推奨:
| ラベル | 目安行数 | 対応 |
|---|---|---|
size/xs | ~50行 | 直接実装 |
size/s | ~100行 | 直接実装 |
size/m | ~200行 | 直接実装（境界） |
size/l | ~400行 | 要分割 |
size/xl | ~800行以上 | 要分割 |
行数見積もり方法
優先順位:
- Issue labelsから推定（
size/*ラベル） - 設計書のコードブロックから推定
- Issueタイトル・本文のキーワードから推定
キーワードベース推定:
| キーワード | 推定行数 |
|---|---|
fix | ~50行 |
update | ~80行 |
add | ~100行 |
refactor | ~150行 |
create | ~150行 |
implement | ~200行 |
分割判定
def should_decompose(issue_id: int) -> bool:
"""分割が必要かどうか判定"""
estimated = estimate_code_lines(issue_id)
return estimated > 200
大きなIssueを見つけた場合
# 1. まず分解コマンドを実行
/decompose-issue 8
# 2. 作成されたSubtaskを実装
# (各Subtaskを順次実装)
リトライポリシー
| 条件 | アクション |
|---|---|
| Issue失敗（1-2回目） | リトライ |
| Issue失敗（3回目） | Draft PRを作成、ユーザーに報告 |
| 複数Issue並列時 | 失敗したIssueのみ報告、他は継続 |
When not to use it
- →When tasks are not implementation-focused
- →When precise, manual line counts are preferred
- →When the project does not use size labels
Limitations
- →Recommends decomposition for issues exceeding 200 lines
- →Estimations are based on keywords and labels
- →Assumes the existence of `size/*` labels for estimation
How it compares
This skill provides a systematic, keyword-driven approach to estimating issue size and identifying decomposition needs, offering a consistent method compared to subjective manual estimations.
Compared to similar skills
issue-size-estimation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| issue-size-estimation (this skill) | 0 | 3mo | Review | Beginner |
| planning-with-files | 233 | 6mo | Review | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by majiayu000
View all by majiayu000 →You might also like
planning-with-files
davila7
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
clickup
civitai
Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.
ma-playbook
alirezarezvani
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.