af-estimate-effort

Estimate task effort by decomposing work into functional areas and roles.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/GainInsightDev/websites --skill af-estimate-effort
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-estimate-effort
Source: https://github.com/GainInsightDev/websites/tree/main/.claude/skills/af-estimate-effort
Command: npx skills add https://github.com/GainInsightDev/websites --skill af-estimate-effort

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for estimating the effort required for tasks and features, breaking down work by functional area and role to ensure comprehensive and accurate estimations.

Core Features & Use Cases

  • Effort Estimation: Estimate tasks in hours and convert to story points using a Fibonacci scale.
  • Role-Based Decomposition: Break down work by functional areas (FE, BE, INFRA, TEST, UX, DOCS) and assign roles.
  • Use Case: When planning a new feature, use this Skill to estimate the total hours for backend development, frontend implementation, testing, and documentation, then convert the total hours into an appropriate number of story points for sprint planning.

Quick Start

Use the af-estimate-effort skill to estimate the effort for implementing a new user authentication flow.

Frequently Asked Questions about af-estimate-effort

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

FAQPage Schema
How do I estimate effort and convert hours to Linear story points?

To estimate effort and convert hours to Linear story points, this approach decomposes work into functional areas and roles, estimates hours per area, then maps total hours to a Fibonacci story point scale.

What is role-based decomposition for software estimation?

Role-based decomposition breaks down feature effort into functional areas like frontend, backend, infrastructure, testing, UX, and documentation, assigning roles to ensure comprehensive and accurate estimations.

How do I break down a feature into functional areas for sprint planning?

Break down feature work by assigning functional areas such as FE, BE, INFRA, TEST, UX, and DOCS. Apply role-based decomposition to estimate hours for each area before sprint planning.

Does this estimation method include heuristics for testing overhead?

Yes, the estimation framework includes specific heuristics for various change types and accounts for testing overhead to provide more accurate effort calculations for sprint planning.

What's the best way to estimate backend and frontend effort separately?

The best way to estimate separate backend and frontend effort is using role-based decomposition, which splits work into distinct functional areas like BE and FE to calculate hours independently before aggregating story points.