agentleFS
Sign inStart free
ShiningPlagueShiningPlague/shiningplague-studio/skills/estimate/SKILL.md

estimate

Skill0 starsChanged 4 months agoMITView on GitHub

Use when estimating effort for a feature, sprint item, or workstream task. Breaks work into sub-tasks, estimates each, identifies risks, and produces a total with confidence range. Fires during sprint planning or when the designer asks 'how long will this take?' ShiningPlague-adopted: full implementation with solo-dev context (no test suite, data-driven architecture) and 1-2 week step sizing.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • +1 more from lilangMax

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Read the governing document (spec, story, or verbal description).

    line 29
  2. Distinctive:

    No test suite — verification time is manual (factor into estimates)

    line 81

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “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

Estimate

🌱 ShiningPlague-adopted. Originally Donchitos (barebones stub); battle-tested on a shipped Godot project. Upstream was a pointer-only file; this version is the full implementation — sub-task breakdown, complexity-based estimates, risk multipliers, solo-dev context.

Effort breakdown and estimation for planning.

If an artifact named here is absent: say so plainly in one line, skip that step, and continue. Never invent the file to satisfy a checklist, and never fail a close because an optional artifact was never created.

Procedure

1. Understand the Work

Read the governing document (spec, story, or verbal description). Identify: what systems are touched, what's new vs modified, dependencies.

2. Break Into Sub-Tasks

Decompose into implementable chunks (each 1-3 days max per CLAUDE.md sprint rules). For each sub-task:

  • Description
  • Systems/files touched
  • Dependencies on other sub-tasks
  • Complexity: Low (routine) / Medium (some unknowns) / High (significant unknowns)

3. Estimate Each Sub-Task

ComplexityEstimate range
Low0.5-1 day
Medium1-2 days
High2-3 days + spike risk

4. Identify Risks

  • Technical unknowns — never done this in Godot before?
  • Dependencies — blocked on another system or decision?
  • Scope ambiguity — design not fully locked?
  • Integration risk — touches multiple autoloads/systems?

Each risk adds a multiplier (1.2x for low, 1.5x for medium, 2x for high).

5. Output

## Estimate: [feature/task name]

### Sub-Tasks
| # | Task | Complexity | Estimate | Dependencies |
|---|---|---|---|---|
| 1 | [task] | Medium | 1-2 days | None |
| 2 | [task] | High | 2-3 days | Task 1 |

### Risks
- [risk 1] — impact: [multiplier]

### Total
- Optimistic: [X] days
- Expected: [Y] days
- Pessimistic: [Z] days (if risks materialise)

### Recommendation
[Whether this fits in a sprint, needs slicing, or needs a spike first]

Solo-Dev Context

  • Solo dev — no parallelism across people, but agent parallelism available
  • No test suite — verification time is manual (factor into estimates)
  • Data-driven architecture — data changes are fast, code changes are slower
  • Each "step" should be 1-2 weeks max

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.

Check your setup, free