Jira Ticket Estimator

Estimate Jira ticket development time across manual and AI-assisted workflows.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/kennyth01/jira-ticket-estimator --skill jira-ticket-estimator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jira Ticket Estimator
Source: https://github.com/kennyth01/jira-ticket-estimator/tree/main/.
Command: npx skills add https://github.com/kennyth01/jira-ticket-estimator --skill jira-ticket-estimator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and inconsistency in Jira ticket estimation, providing clear, data-driven time breakdowns for both manual and AI-assisted development workflows. It helps teams accurately plan sprints, forecast project timelines, and understand the true cost of work, reducing delays and improving predictability.

Core Features & Use Cases

  • Dual Workflow Estimation: Get detailed time estimates for both traditional manual development and AI-assisted coding processes, highlighting potential time savings.
  • Comprehensive Phase Breakdowns: Estimates are broken down into 6 manual phases (Planning & Design, Implementation, Self Review, Testing, Code Review, Deployment) or 7 AI-assisted phases, mirroring real-world development.
  • Intelligent Classification: Automatically categorizes tasks (Net-New, Enhancement, Refactor, Bug Fix, Spike) and project types (Monolithic, Serverless, Frontend, Full-Stack, Mobile) to tailor estimates.
  • Complexity-Driven Sizing: Scores tickets based on scope, technical complexity, testing, risk, and dependencies, then translates to T-shirt sizes and Fibonacci story points.
  • Overhead Detection: Automatically identifies and adds time for common organizational overheads like database changes or security reviews.
  • Use Case: Ideal for sprint planning, project managers needing accurate forecasts, and development teams looking to optimize their estimation process and leverage AI effectively.

Quick Start

Estimate PROJ-123 for our Laravel monolith

Frequently Asked Questions about Jira Ticket Estimator

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

FAQPage Schema
How do I estimate Jira ticket development time accurately?

Jira ticket estimation breaks down into 6 manual phases (Planning & Design, Implementation, Self Review, Testing, Code Review, Deployment) or 7 AI-assisted phases. The Skill classifies task type, scores complexity based on scope and dependencies, and applies phase-by-phase formulas to generate estimates with detailed breakdowns for sprint planning.

Can I get separate time estimates for manual development versus AI-assisted coding?

Yes, dual workflow estimation provides distinct time breakdowns for both traditional manual development and AI-assisted processes, highlighting potential time savings and comparing phase durations across workflows.

How does the Skill handle different project types and task classifications?

The Skill intelligently classifies projects (Monolithic, Serverless, Frontend, Full-Stack, Mobile, Test Automation) and tasks (Net-New, Enhancement, Refactor, Bug Fix, Spike), then tailors estimates by adjusting complexity scores and applying architecture-specific overhead activities.

What overhead factors does estimation include?

Estimation automatically detects and adds time for organizational overheads like database changes, security reviews, and file touch overhead, integrating heuristics to account for common blockers affecting development time.

How do story points and complexity scoring work?

Tickets are scored on scope, technical complexity, testing requirements, risk, and dependencies, then translated to T-shirt sizes and Fibonacci story points, providing standardized effort sizing for sprint capacity planning.