estimate

Étoiles8

Forks0

Mis à jour15 avril 2026 à 20:51

Estimation workflow for a feature or task. Breaks the task into sub-tasks, estimates each, sums with contingency buffer.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

CodePhobiia

CodePhobiia/claude-roblox-game-studio

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	estimate
description	Estimation workflow for a feature or task. Breaks the task into sub-tasks, estimates each, sums with contingency buffer.

/estimate — Task Estimation

Delegate to: producer (with lead-programmer for tech estimates)

Steps

1. Gather Context

Ask: "What task / feature do you want to estimate?"

2. Break Down Into Sub-Tasks

For a typical feature, list:

Design: GDD writing (0.5-2 days)
Implementation: Code writing (1-10 days depending on scope)
Art assets: If needed (varies wildly)
Integration: Hooking into existing systems (0.5-2 days)
Testing: QA plan + execution (0.5-2 days)
Polish: Rough edges, edge cases (0.5-1 day)
Review: Code review, design review (0.5 day)

3. Estimate Each Sub-Task

Use T-shirt sizing for unclear items, hours for clear items:

XS: < 2 hours (trivial)
S: 2-8 hours (simple)
M: 1-3 days (moderate)
L: 3-7 days (complex)
XL: 1-2 weeks (very complex, consider breaking down)
XXL: 2+ weeks (must break down further before proceeding)

4. Apply Contingency Buffer

For tasks with uncertainty: +30-50%
For tasks in new territory: +50-100%
For tasks with external dependencies: +variable (explicit risk note)
For bug fixes: +20% (things hide)

5. Sum and Sanity Check

Compare to available capacity in current sprint
Flag if > 40% of sprint capacity (single task dominating the sprint)
Flag if total breakdown doesn't match vague intuition

6. Present Estimate

# Estimate: [Feature Name]

## Sub-tasks
| Task | Size | Hours (est) | Risk |
|------|------|-------------|------|
| Design GDD | S | 6 | Low |
| Implement core | M | 16 | Medium |
| Implement UI | S | 8 | Low |
| Test + polish | S | 6 | Low |
| Review + iterate | S | 4 | Low |

**Subtotal**: 40 hours
**Contingency** (30%): 12 hours
**Total estimate**: ~52 hours (~6.5 working days)

## Risks
1. [Risk 1 — how it affects estimate]
2. [Risk 2]

## Assumptions
- [Assumption 1]
- [Assumption 2]

## Dependencies
- [Other tasks/systems this depends on]

Output

Present estimate to user. If too large, suggest splitting the feature. Save estimates to production/sprints/estimates/ when approved.

Plus depuis ce dépôt

même dépôt

doctor

CodePhobiia/claude-roblox-game-studio

Run a comprehensive health check on the repo. Verifies README counts match reality, promised files exist, no unresolved placeholders, wiki index is synced, toolchain configs are valid, and agent roster is accurate. Use after making structural changes or before publishing.

2026-04-168

start

CodePhobiia/claude-roblox-game-studio

Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".

2026-04-168

asset-from-image

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset from a reference image using Blender MCP's image-to-3D AI (Hyper3D). Optimizes for Roblox and exports FBX.

2026-04-168

generate-asset

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset for Roblox using Blender MCP. Creates models from text descriptions via AI (Hyper3D/Hunyuan3D) or downloads from PolyHaven/Sketchfab, optimizes for Roblox constraints, and exports FBX.

2026-04-168

studio-inspect

CodePhobiia/claude-roblox-game-studio

Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.

2026-04-168

studio-screenshot

CodePhobiia/claude-roblox-game-studio

Capture a screenshot of the current Roblox Studio viewport and analyze it. Use for visual verification of UI, lighting, level layout, and general game appearance.

2026-04-168

/estimate — Task Estimation

Delegate to: producer (with lead-programmer for tech estimates)

Steps

1. Gather Context

Ask: "What task / feature do you want to estimate?"

2. Break Down Into Sub-Tasks

For a typical feature, list:

Design: GDD writing (0.5-2 days)

Implementation: Code writing (1-10 days depending on scope)

Art assets: If needed (varies wildly)

Integration: Hooking into existing systems (0.5-2 days)

Testing: QA plan + execution (0.5-2 days)

Polish: Rough edges, edge cases (0.5-1 day)

Review: Code review, design review (0.5 day)

3. Estimate Each Sub-Task

Use T-shirt sizing for unclear items, hours for clear items:

XS: < 2 hours (trivial)

S: 2-8 hours (simple)

M: 1-3 days (moderate)

L: 3-7 days (complex)

XL: 1-2 weeks (very complex, consider breaking down)

XXL: 2+ weeks (must break down further before proceeding)

4. Apply Contingency Buffer

For tasks with uncertainty: +30-50%

For tasks in new territory: +50-100%

For tasks with external dependencies: +variable (explicit risk note)

For bug fixes: +20% (things hide)

5. Sum and Sanity Check

Compare to available capacity in current sprint

Flag if > 40% of sprint capacity (single task dominating the sprint)

Flag if total breakdown doesn't match vague intuition

6. Present Estimate

# Estimate: [Feature Name] ## Sub-tasks | Task | Size | Hours (est) | Risk | |------|------|-------------|------| | Design GDD | S | 6 | Low | | Implement core | M | 16 | Medium | | Implement UI | S | 8 | Low | | Test + polish | S | 6 | Low | | Review + iterate | S | 4 | Low | **Subtotal**: 40 hours **Contingency** (30%): 12 hours **Total estimate**: ~52 hours (~6.5 working days) ## Risks 1. [Risk 1 — how it affects estimate] 2. [Risk 2] ## Assumptions - [Assumption 1] - [Assumption 2] ## Dependencies - [Other tasks/systems this depends on]

Output

Present estimate to user. If too large, suggest splitting the feature. Save estimates to production/sprints/estimates/ when approved.