estimate-jira_skill

Overview

This skill estimates complexity, effort, and risks for JIRA tickets, features, or projects and produces a structured estimation report. It delivers time ranges, dependency mapping, risk analysis, and a list of known unknowns to support planning and prioritization. Use it when you ask to "estimate", "size", or "analyze complexity" of work items.

How this skill works

Provide the JIRA ticket content (markdown preferred) and the agent analyzes scope, acceptance criteria, and missing information. It identifies impacted areas, enumerates ambiguities and implementation choices, and produces a consistent estimation report with breakdowns for implementation, testing, docs, and review. When choices materially affect estimates, the skill prompts for structured clarification before finalizing numbers.

When to use it

• Sizing a new feature or enhancement before sprint planning
• Estimating effort for a bug fix or regression with unclear scope
• Assessing risk and dependencies for a cross-team change
• Preparing time and resource ranges for stakeholder approval
• Validating whether a ticket is ready for implementation (refinement)

Best practices

• Always supply full ticket text and acceptance criteria in markdown
• Flag any missing constraints or performance targets up front
• Answer structured ambiguity questions to reduce estimate uncertainty
• Expect estimates as ranges (days/hours) and with explicit assumptions
• Include testing, docs, and wrapper updates in scope unless excluded

Example use cases

• Estimate a new charting feature that affects core rendering and wrappers
• Size a refactor that may impact multiple packages and public types
• Analyze effort for adding visual regression tests and documentation
• Assess risk for changing a public API used by downstream packages
• Provide quick high-confidence estimate when ticket is well-specified