ホーム/プロダクト/task-estimation
T

task-estimation

by @supercent-iov
4.5(420)

このスキルはタスク見積もりに使用され、スプリント計画、ロードマップ作成、リソース計画、予算編成、リスク評価を含み、チームが作業とリソースを合理的に割り当てるのに役立ちます。

story-pointsplanning-pokeragile-estimationproject-planningeffort-estimationGitHub
インストール方法
npx skills add supercent-io/skills-template --skill task-estimation
compare_arrows

Before / After 効果比較

1
使用前

タスクの見積もりが場当たり的で、統一された基準や方法が不足していたため、見積もり誤差が大きく、プロジェクト計画の頻繁な調整、不合理なリソース配分が発生し、最終的にプロジェクトの納期に影響を与えていました。

使用後

ストーリーポイント(Story Points)などの相対見積もり手法を採用し、フィボナッチ数列と組み合わせて見積もりを行い、明確な見積もりガイドラインを策定しました。これにより、タスク見積もりの精度とチームの作業量に対する共通認識が向上し、プロジェクトの予測可能性が高まりました。

SKILL.md

task-estimation

Task Estimation When to use this skill Sprint Planning: Decide what work to include in the sprint Roadmap creation: Build long-term plans Resource planning: Estimate team size and schedule Instructions Step 1: Story Points (relative estimation) Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21 ## Story Point guidelines ### 1 Point (Very Small) - Example: text change, constant value update - Time: 1-2 hours - Complexity: very low - Risk: none ### 2 Points (Small) - Example: simple bug fix, add logging - Time: 2-4 hours - Complexity: low - Risk: low ### 3 Points (Medium) - Example: simple CRUD API endpoint - Time: 4-8 hours - Complexity: medium - Risk: low ### 5 Points (Medium-Large) - Example: complex form implementation, auth middleware - Time: 1-2 days - Complexity: medium - Risk: medium ### 8 Points (Large) - Example: new feature (frontend + backend) - Time: 2-3 days - Complexity: high - Risk: medium ### 13 Points (Very Large) - Example: payment system integration - Time: 1 week - Complexity: very high - Risk: high - Recommended: Split into smaller tasks ### 21+ Points (Epic) - Required: Must be split into smaller stories Step 2: Planning Poker Process: Product Owner explains the story Team asks questions Everyone picks a card (1, 2, 3, 5, 8, 13) Reveal simultaneously Explain highest/lowest scores Re-vote Reach consensus Example: Story: "Users can upload a profile photo" Member A: 3 points (simple frontend) Member B: 5 points (image resizing needed) Member C: 8 points (S3 upload, security considerations) Discussion: - Use an image processing library - S3 is already set up - File size validation needed Re-vote → consensus on 5 points Step 3: T-Shirt Sizing (quick estimation) ## T-Shirt sizes - XS: 1-2 Story Points (within 1 hour) - S: 2-3 Story Points (half day) - M: 5 Story Points (1-2 days) - L: 8 Story Points (1 week) - XL: 13+ Story Points (needs splitting) When to use: - Initial backlog grooming - Rough roadmap planning - Quick prioritization Step 4: Consider risk and uncertainty Estimation adjustment: interface TaskEstimate { baseEstimate: number; // base estimate risk: 'low' | 'medium' | 'high'; uncertainty: number; // 0-1 finalEstimate: number; // adjusted estimate } function adjustEstimate(estimate: TaskEstimate): number { let buffer = 1.0; // risk buffer if (estimate.risk === 'medium') buffer *= 1.3; if (estimate.risk === 'high') buffer *= 1.5; // uncertainty buffer buffer *= (1 + estimate.uncertainty); return Math.ceil(estimate.baseEstimate * buffer); } // Example const task = { baseEstimate: 5, risk: 'medium', uncertainty: 0.2 // 20% uncertainty }; const final = adjustEstimate(task); // 5 * 1.3 * 1.2 = 7.8 → 8 points Output format Estimation document template ## Task: [Task Name] ### Description [work description] ### Acceptance Criteria - [ ] Criterion 1 - [ ] Criterion 2 - [ ] Criterion 3 ### Estimation - Story Points: 5 - T-Shirt Size: M - Estimated Time: 1-2 days ### Breakdown - Frontend UI: 2 points - API Endpoint: 2 points - Testing: 1 point ### Risks - Uncertain API response time (medium risk) - External library dependency (low risk) ### Dependencies - User authentication must be completed first ### Notes - Need to discuss design with UX team Constraints Required rules (MUST) Relative estimation: Relative complexity instead of absolute time Team consensus: Agreement from the whole team, not individuals Use historical data: Plan based on velocity Prohibited (MUST NOT) Pressuring individuals: Estimates are not promises Overly granular estimation: Split anything 13+ points Turning estimates into deadlines: estimate ≠ commitment Best practices Break Down: Split big work into smaller pieces Reference Stories: Reference similar past work Include buffer: Prepare for the unexpected References Scrum Guide Planning Poker Story Points Metadata Version Current version: 1.0.0 Last updated: 2025-01-01 Compatible platforms: Claude, ChatGPT, Gemini Tags #estimation #agile #story-points #planning-poker #sprint-planning #project-management Examples Example 1: Basic usage Example 2: Advanced usageWeekly Installs10.3KRepositorysupercent-io/sk…templateGitHub Stars53First SeenJan 24, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex10.2Kgemini-cli10.2Kopencode10.2Kgithub-copilot10.1Kcursor10.1Kamp10.1K

ユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数10.5K
評価4.5 / 5.0
バージョン
更新日2026年5月9日
比較事例1 件

ユーザー評価

4.5(420)
5
36%
4
49%
3
14%
2
1%
1
0%

この Skill を評価

0.0

対応プラットフォーム

🔧Claude Code
🔧OpenClaw
🔧OpenCode
🔧Codex
🔧Gemini CLI
🔧GitHub Copilot
🔧Amp
🔧Kimi CLI

タイムライン

作成2026年3月17日
最終更新2026年5月9日