agentleFS
Tony363Tony363/SuperClaude/.claude/skills/sc-estimate/SKILL.md

sc-estimate

Skill19 starsChanged 8 months agoMITView on GitHub

Provide development estimates for tasks, features, or projects with intelligent analysis. Use when planning timelines, assessing complexity, or scoping resources.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Track: - Document for accuracy improvement

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Development Estimation Skill

Systematic estimation with confidence intervals and risk assessment.

Quick Start

# Time estimate with breakdown
/sc:estimate "auth system" --type time --unit days --breakdown

# Complexity assessment
/sc:estimate "microservices migration" --type complexity

# Effort analysis
/sc:estimate "performance optimization" --type effort --unit hours

Behavioral Flow

  1. Analyze - Examine scope, complexity, and dependencies
  2. Calculate - Apply estimation methodology with benchmarks
  3. Validate - Cross-reference with domain expertise
  4. Present - Provide breakdown with confidence intervals
  5. Track - Document for accuracy improvement

Flags

FlagTypeDefaultDescription
--typestringtimetime, effort, complexity
--unitstringdayshours, days, weeks
--breakdownboolfalseShow detailed breakdown

Personas Activated

  • architect - Design complexity assessment
  • performance - Optimization effort analysis
  • project-manager - Timeline and resource planning

MCP Integration

  • PAL MCP - Multi-perspective estimate validation

Evidence Requirements

This skill does NOT require hard evidence. Deliverables are:

  • Estimates with confidence intervals
  • Risk factor identification
  • Breakdown documentation

Estimation Types

Time (--type time)

  • Calendar duration estimates
  • Milestone planning
  • Deadline assessment

Effort (--type effort)

  • Person-hours/days required
  • Resource allocation guidance
  • Team capacity planning

Complexity (--type complexity)

  • Technical complexity scoring
  • Risk factor identification
  • Dependency mapping

Confidence Levels

Estimates include confidence intervals:

  • High (85-95%) - Well-understood scope
  • Medium (70-84%) - Some unknowns
  • Low (50-69%) - Significant uncertainty

Examples

Feature Estimation

/sc:estimate "user authentication" --type time --unit days --breakdown
# Breakdown: DB design (2d) + API (3d) + UI (2d) + Tests (1d)
# Total: 8 days @ 85% confidence

Complexity Assessment

/sc:estimate "monolith to microservices" --type complexity --breakdown
# Architecture complexity with risk factors
# Dependency mapping and migration phases

Effort Analysis

/sc:estimate "API performance optimization" --type effort --unit hours
# Profiling (4h) + Analysis (6h) + Implementation (16h) + Testing (8h)
# Total: 34 hours @ 75% confidence

Tool Coordination

  • Read/Grep/Glob - Codebase complexity analysis
  • TodoWrite - Estimation breakdown tracking
  • Task - Multi-domain estimation delegation
  • Bash - Dependency and project analysis

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.