estimate

Break tasks into sub-tasks and calculate estimates with contingency buffers.

8|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill estimate-codephobiia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/CodePhobiia/claude-roblox-game-studio/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill estimate-codephobiia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimation of features or tasks is often ambiguous and delays planning; this Skill provides a structured approach to break work into sub-tasks, estimate each, and sum with a contingency buffer.

Core Features & Use Cases

  • Sub-task breakdown with sizes (XS-XXL)
  • Contingency calculation and risk notes
  • Output-ready estimates for sprint planning and roadmaps
  • Reusable templates for future tasks

Quick Start

Provide the feature name and scope to generate a detailed estimate.

Frequently Asked Questions about estimate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured estimate for sprint planning?

To create a structured estimate for sprint planning, provide a task scope and sub-tasks with sizes from XS to XXL. The system calculates a subtotal, applies a contingency buffer, and outputs a structured estimate with risk notes and a final total.

What is a contingency buffer and how does it apply to task estimation?

A contingency buffer in task estimation is an added time margin calculated to offset identified risks and assumptions. It is applied to the subtotal of sub-task sizes to produce a final, realistic total estimate for project scoping.

Can I estimate effort across design, implementation, and testing phases?

Yes, you can quantify effort across design, implementation, testing, and polish phases. You need to supply a list of sub-tasks categorized by these phases, along with their sizes, associated risks, and dependencies for accurate calculation.

What do I need to start estimating a feature or task?

To start estimating a feature or task, you need to define the feature name, its scope, a list of sub-tasks, associated risks, assumptions, and dependencies. This input generates an output-ready estimate with subtotal, contingency, and total.

What is the best way to break down project scope into sub-tasks?

The best way to break down project scope is to divide the feature into actionable sub-tasks and assign each a size from XS to XXL. This structured approach quantifies individual effort and clarifies dependencies for accurate roadmap estimation.