Skip to content
JIRA Story Point Estimator logo

JIRA Story Point Estimator

Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?

SKILL.md

Full skill instructions

JIRA Story Point Estimator Skill

When to Use This Skill

Activate this skill when the user:

  • Asks "estimate this ticket" or "how many story points?"
  • Asks to "size" or "point" a ticket
  • Asks "what should this be pointed at?"
  • Wants help with sprint planning estimation
  • Asks "is X points right for this ticket?"
  • Reviews a ticket that needs story points

Story Point Scale Reference

HyperFleet uses a modified Fibonacci sequence for story points:

PointsMeaningTypical ScopeNotes
0Tracking OnlyQuick/​easy task with stakeholder valueRarely used. For tasks worth tracking but with negligible effort compared to a 1-pointer
1TrivialOne-line change, extremely simple taskThe smallest issue possible - everything scales from here. No risk, very low effort, very low complexity
3StraightforwardTime consuming but fairly straightforward workDoesn't have to be complex, but usually time consuming. Minor risks possible
5MediumRequires investigation, design, collaborationProbably needs discussion with others. Can be quite time consuming or complex. Risks involved
8LargeBig task requiring investigation and designRequires collaboration with others. Solution can be quite challenging. Risks are expected. Design doc required
13Too LargeShould be split into smaller storiesIdeally, this shouldn't be used. If you see an issue this big, it must be broken down

Estimation Methodology

Step 1: Fetch Ticket Details

jira issue view TICKET-KEY --plain 2>/​dev/​null

Step 2: Analyze Complexity Factors

Scope Indicators (examine description and acceptance criteria):

  • Number of acceptance criteria
  • Number of components/​files likely affected
  • Integration points mentioned
  • Testing requirements

Complexity Indicators:

  • New feature vs. modification vs. bug fix
  • Requires new patterns or unfamiliar technology
  • External dependencies (APIs, services)
  • Database/​schema changes
  • Security implications
  • Documentation requirements

Risk Indicators:

  • Ambiguity in requirements
  • Dependencies on other tickets
  • Time-sensitive (blocks other work)
  • Requires coordination with other teams

Step 3: Find Similar Historical Tickets

Search for comparable completed tickets:

jira issue list -q"project = HYPERFLEET AND status = Done AND type = Story" --plain 2>/​dev/​null | head -20
jira issue list -q"project = HYPERFLEET AND status = Done AND 'Story Points' is not EMPTY AND type = Story" --plain 2>/​dev/​null | head -20

Step 4: Provide Estimation

Output Format

Estimation for: TICKET-KEY

Summary: [Ticket title] Type: [Story/​Task/​Bug]


Complexity Analysis
FactorAssessmentImpact
Scope[Small/​Medium/​Large][Description]
Technical Complexity[Low/​Medium/​High][Why]
Dependencies[None/​Few/​Many][List if any]
Testing Effort[Minimal/​Moderate/​Extensive][Why]
Risk/​Uncertainty[Low/​Medium/​High][Why]

Recommendation

Suggested Story Points: X

Confidence Level: [High/​Medium/​Low]

Reasoning:

  • [Primary factor 1]
  • [Primary factor 2]
  • [Comparison to similar work]

Similar Completed Tickets (for reference)
TicketSummaryPointsSimilarity
TICKET-A[Summary]5High - similar scope
TICKET-B[Summary]3Medium - simpler version

Considerations
  • If higher: [What would make this larger]
  • If lower: [What would make this smaller]
  • Break-down suggestion: [If 13+ points, suggest how to split]

Setting Story Points

Once agreed, set story points using:

jira issue edit TICKET-KEY --custom story-points=X --no-input

Or for Story Point Estimate field (Next-gen projects):

jira issue edit TICKET-KEY --custom story-point-estimate=X --no-input

Team Calibration Notes

When estimating, consider:

  • Team's typical velocity (points completed per sprint)
  • Recent similar work and how long it actually took
  • Team familiarity with the codebase area
  • Current sprint load and focus

Anti-Patterns to Flag

  • Anchoring: Don't let existing (wrong) estimates bias you
  • Scope Creep: Point what's written, not what might be added
  • Hero Estimates: Assume average team member, not expert
  • Planning Fallacy: Add buffer for unknowns
  • Story Point Inflation: Keep consistent with team baseline

More Security skills

supabase logo
Security

supabase

Handles the full Supabase workflow from schema changes to deployment, with built-in security guardrails that catch common traps like RLS...

2.7K 308.9K
View

Comprehensive guides and best practices for Neon Serverless Postgres, covering setup, connection methods, authentication, and platform APIs.

98 216.2K
View

Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.

462 163.8K
View

A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.

462 127.7K
View

Official skill for integrating Firebase AI Logic (Gemini API) into web applications. Covers setup, multimodal inference, structured output, and security.

462 125.1K
View

Complete Better Auth server and client setup with database adapters, session management, plugins, and security configuration.

222 118.2K
View

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

31.9K 116.1K
View
cloudflare logo
Security

cloudflare

Complete Cloudflare platform integration with decision trees for compute, storage, AI, networking, security, and infrastructure-as-code.

3K 110.7K
View

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

253 103K
View
gws-gmail logo
Security

gws-gmail

Send, read, and manage Gmail messages, drafts, labels, and account settings.

31.2K 78.9K
View

Comprehensive website auditing across 230+ rules in 21 categories including SEO, performance, security, and accessibility.

94 72.3K
View
gws-shared logo
Security

gws-shared

Shared authentication, CLI syntax, and output formatting patterns for gws Google Workspace commands.

31.2K 63.4K
View

Security AI tools

StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
GeoSpy logo
Security

GeoSpy

GeoSpy: Pricing, Features, FAQs, and Alternatives for AI Teams

Free
View

Detect AI-generated voices to protect against audio fraud.

Paid
View

Ensure Your Content's Originality with AI Plagiarism Checker

Freemium
View
Img Upscaler logo
Security

Img Upscaler

Upscale images by 400% without quality loss

Freemium
View
AICheatCheck logo
Security

AICheatCheck

Accurately Detect AI-Generated Content with TheChecker.AI

Free
View
D
Security

Detect GPT

Chrome extension that detects and flags AI-generated content

Free
View