sc-estimate — Claude Code skill: dev estimates with confidence
sc-estimate turns a task, feature or migration into a time, effort or complexity estimate with a confidence range and the risks behind it.
MIT 184 installs ★ 21 updated 2026-06-29
npx skills add Tony363/SuperClaude --skill sc-estimate -a claude-codeWhat sc-estimate does
The skill walks a task through a fixed chain: scope and dependency analysis, a calculation against benchmarks, a cross-check with domain knowledge, a written breakdown, then a record you can compare with what actually shipped. Mode comes from --type: time for calendar dates and milestones, effort for person-hours, complexity for technical difficulty and a dependency map.
Each result carries a confidence range — 85–95% when scope is clear, 70–84% with open unknowns, 50–69% when a lot is still unsettled. --breakdown adds the per-part split, --unit sets hours, days or weeks, and days is the default. Repo context comes from Read/Grep/Glob and Bash; TodoWrite keeps the steps in order.
The cross-check runs through PAL MCP, so without that server connected you get a single calculation and no second opinion. Architecture, performance and project-management personas step in depending on what you are estimating.
What it helps with
- scope a feature before sprint planning
- turn a vague migration into phases with dependencies
- hand a client a range instead of one number
- budget person-hours for API tuning
- compare the estimate against what shipped
Example prompts for the agent
- Estimate
auth systemin days and show the split:/sc:estimate "auth system" --type time --unit days --breakdown - How hard is the monolith-to-microservices move:
/sc:estimate "microservices migration" --type complexity --breakdown - Hours needed for API speed work:
/sc:estimate "performance optimization" --type effort --unit hours
How to install sc-estimate
1Skills CLI (Vercel)
npx skills add Tony363/SuperClaude --skill sc-estimate -a claude-code2Manually: put the files in place
~/.claude/skills/sc-estimate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sc-estimate/
1Skills CLI (Vercel)
npx skills add Tony363/SuperClaude --skill sc-estimate -a codex2Manually: put the files in place
.agents/skills/sc-estimate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Tony363/SuperClaude --skill sc-estimate -a cursor2Manually: put the files in place
.cursor/skills/sc-estimate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Tony363/SuperClaude .claude/skills/sc-estimate2Manually: put the files in place
.github/skills/sc-estimate/SKILL.md1Skills CLI (Vercel)
npx skills add Tony363/SuperClaude --skill sc-estimate -a gemini-cli2Platform CLI
gemini skills install https://github.com/Tony363/SuperClaude --path .claude/skills/sc-estimateManually: put the files in place
.devin/skills/sc-estimate/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Tony363/SuperClaude --skill sc-estimate -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sc-estimate
How do I install sc-estimate in Claude Code?
Run npx skills add Tony363/SuperClaude --skill sc-estimate -a claude-code. The skill file lands at ~/.claude/skills/sc-estimate/SKILL.md.
What does sc-estimate do?
It produces a time, effort or complexity estimate, with a per-part breakdown, a confidence range and the risk factors behind the number.
What do the confidence percentages mean?
85–95% means the scope is well understood, 70–84% leaves some unknowns open, 50–69% signals real uncertainty. The range tells you how much weight the estimate can carry.
Source text
SKILL.md · MIT
--- name: sc-estimate description: 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
© Tony363 · MIT · Tony363/SuperClaude