How do I install the Sc Estimate skill?

Run npx skillmds add majiayu000/sc-estimate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sc Estimate safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sc Estimate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sc Estimate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sc Estimate?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sc Estimate by majiayu000 — Agent Skill

Name: Sc Estimate
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

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

Flags

Flag	Type	Default	Description
`--type`	string	time	time, effort, complexity
`--unit`	string	days	hours, days, weeks
`--breakdown`	bool	false	Show 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

---name: sc-estimatedescription: Provide development estimates for tasks, features, or projects with intelligent analysis. Use when planning timelines, assessing complexity, or scoping resources.--- # Development Estimation Skill Systematic estimation with confidence intervals and risk assessment. ## Quick Start ```bash # 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 | Flag | Type | Default | Description | |------|------|---------|-------------| | `--type` | string | time | time, effort, complexity | | `--unit` | string | days | hours, days, weeks | | `--breakdown` | bool | false | Show 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

Frequently asked questions