skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
dralgorhythm/claude-agentic-framework59 installs

estimating-work

Estimate effort for development tasks. Use when planning sprints, roadmaps, or project timelines. Covers story points, relative estimation, and uncertainty.

How do I install this agent skill?

npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill estimating-work
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides educational content and guidelines for estimating software development work. It contains only static documentation and poses no security risk.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

What does this agent skill do?

Estimating Work

Estimation Approaches

Story Points

Relative complexity, not time.

PointsComplexity
1Trivial, well understood
2Simple, minor unknowns
3Moderate complexity
5Complex, some unknowns
8Very complex, significant unknowns
13Extremely complex, many unknowns
21+Too big, needs decomposition

T-Shirt Sizing

For high-level estimates.

SizeRelative Effort
XSHours
S1-2 days
M3-5 days
L1-2 weeks
XL2-4 weeks

Estimation Factors

Consider:

  • Complexity: How difficult is the problem?
  • Uncertainty: How much is unknown?
  • Effort: How much work is involved?
  • Risk: What could go wrong?

Estimation Techniques

Planning Poker

  1. Present the task
  2. Everyone selects estimate privately
  3. Reveal simultaneously
  4. Discuss outliers
  5. Re-estimate if needed

Three-Point Estimation

Expected = (Optimistic + 4×Likely + Pessimistic) / 6

Reference Stories

Keep calibration stories:

  • "This 3-point story took 2 days"
  • "This 8-point story took a week"

Common Pitfalls

  • Anchoring: First estimate biases others
  • Optimism: Underestimating unknowns
  • Scope Creep: Original estimate doesn't match final scope
  • Ignoring Overhead: Code review, testing, deployment

Tips

  1. Estimate in ranges, not points
  2. Include buffer for unknowns
  3. Track actual vs. estimated
  4. Re-estimate when scope changes
  5. Don't estimate in hours (use relative sizing)

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/dralgorhythm/claude-agentic-framework/estimating-work">View estimating-work on skillZs</a>