estimate-task

Score development tasks on a 1-3 complexity scale for effort estimation.

5|Updated Feb 4, 2026

Search Tags:#planning #complexity #sprint #software-engineering #estimate #task-scoring

Ready to run

npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill estimate-task-hirogakatageri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimate-task
Source: https://github.com/HirogaKatageri/hirokata-cc-marketplace/tree/main/plugins/cc-develop-plugin/skills/estimate-task
Command: npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill estimate-task-hirogakatageri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a consistent method to assign a numeric complexity score to development tasks, enabling faster planning and more accurate sprint estimation.

Core Features & Use Cases

Three-level scoring (1/2/3) to quickly categorize tasks by effort and risk.
Guided decision framework to help teams decide when to break down tasks and plan iterations.
Use cases: estimate bug fixes, new features, refactors, and architectural spikes to inform prioritization and capacity planning.

Quick Start

Provide a task description like "Implement feature X with Y requirements." The skill returns a score and rationale you can use to plan the effort.

Frequently Asked Questions about estimate-task

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

FAQPage Schema

How do I estimate software development tasks for sprint planning?▼

To estimate tasks for sprint planning, you score development task effort using a 3-level scale (1/2/3). This method provides a quick, actionable complexity score and rationale to categorize effort and risk, streamlining capacity planning across software projects.

What is task complexity scoring and when do I need it?▼

Task complexity scoring is a method to assign a numeric value to development effort. You need it during planning and sprint estimation to consistently categorize bug fixes, new features, refactors, and architectural spikes for faster prioritization.

Can I use plain text descriptions to score bug fixes and new features?▼

Yes, you can use plain task descriptions to score bug fixes and new features. The skill requires no external tools and processes plain text directly to produce a guided complexity score and rationale for your software engineering tasks.

What's the best way to decide when to break down tasks in a sprint?▼

The best way to decide when to break down tasks is to use a guided decision framework with a 3-level complexity scale. Scoring tasks helps teams quickly identify high-effort items and plan iterations for more accurate capacity planning.

Does task complexity scoring require external tools or integrations?▼

No, task complexity scoring requires no external tools or integrations. It is designed to work independently with plain task descriptions to produce a quick, actionable score and rationale, streamlining software project planning.