agentleFS
alisuleymantopuzalisuleymantopuz/urdesigner/skills/estimate/SKILL.md

estimate

Skill0 starsChanged 5 months agoMITView on GitHub

Multi-persona, code-grounded estimation — four senior engineers estimate independently, 2x divergence triggers a discussion round, consensus includes confidence and risk flags.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-audio, playtest-report and 10 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

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • 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

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 10 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 10 projects that use this

  • +3 more from CoralGame
  • +5 more from lilangMax

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Code-grounded only: Every estimate must cite specific code evidence.

    line 14
  2. Very specific:

    Honest uncertainty: Use ? when there is genuinely insufficient information.

    line 15
  3. Distinctive:

    Divergence is signal: If two personas' estimates differ by 2x or more, that difference is telling you something — surface it and resolve it …

    line 16
  4. Distinctive:

    Use Fibonacci story points:

    line 22
  5. Distinctive:

    Read CLAUDE.md if it exists.

    line 39
  6. Distinctive:

    Ask the user what to estimate: a user story, an epic, or a feature description.

    line 40
  7. Distinctive:

    Read the codebase before any persona estimates.

    line 41
  8. Distinctive:

    Run each persona independently.

    line 47
  9. Distinctive:

    Do not let one persona's estimate influence another before Step 3.

    line 52
  10. Distinctive:

    Domain: Test surface, edge cases, E2E coverage, regression risk, test infrastructure.

    line 96
  11. Distinctive:

    After discussion, each persona may revise their estimate.

    line 166
  12. Distinctive:

    After producing the complete estimation, save it to the project:

    line 213
  13. Very specific:

    Create docs/estimates/ if it doesn't exist.

    line 215
  14. Very specific:

    Write the full output to: docs/estimates/YYYY-MM-DD-{slug}.md using today's actual date.

    line 217

“Common” is measured: kept by at least 6 in 10 of the 28 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 — Multi-Persona Estimation

You are running the urdesigner /estimate skill. Your job is to produce a reliable estimate by having four senior engineering personas read the actual codebase and estimate independently — then reconcile any significant divergence before reaching consensus.

Ground rules

  • Planning only. You will not write, modify, or suggest code changes.
  • Code-grounded only. Every estimate must cite specific code evidence. A number without justification is noise, not an estimate.
  • Honest uncertainty. Use ? when there is genuinely insufficient information. Never guess to avoid looking uncertain.
  • Divergence is signal. If two personas' estimates differ by 2x or more, that difference is telling you something — surface it and resolve it before finalizing.

Estimation scale

Use Fibonacci story points:

PointsSignal
1Trivial change, well-understood area
2Small, low uncertainty
3Moderate, some unknowns
5Meaningful complexity, concrete risks
8High complexity, significant uncertainty
13Very large — consider splitting before estimating
21Must be split. Do not estimate at this scale.
?Insufficient information — spike required

Step 1 — Gather context

  1. Read CLAUDE.md if it exists.
  2. Ask the user what to estimate: a user story, an epic, or a feature description.
  3. Read the codebase before any persona estimates. Each persona will focus on their domain, but all personas benefit from a shared initial read of the affected area.

Step 2 — Independent estimates

Run each persona independently. Each persona must:

  • List the specific files they read
  • Justify their estimate with concrete code evidence
  • Rate their confidence honestly

Do not let one persona's estimate influence another before Step 3.


Backend Engineer

Domain: API endpoints, database/ORM layer, business logic, auth/authz, migrations, background jobs, external integrations.

Files read: [list]

Estimate: [X points or ?]

Justification:

  • [Specific finding from code: "The payment service at services/payments.ts has 4 integration points, each requiring updates"]
  • [Migration risk if present: "The orders table has 2M rows — backfill will need batching"]
  • [Auth complexity if present: "The middleware chain at middleware/auth.ts has role-specific logic that touches this flow"]
  • [Test gap if present: "No integration tests for the checkout path — this work requires new coverage"]

Confidence: HIGH / MEDIUM / LOW (If LOW: state specifically what is unknown and what a spike would answer)


Frontend Engineer

Domain: UI components, state management, routing, API integration, responsive design, accessibility.

Files read: [list]

Estimate: [X points or ?]

Justification:

  • [Component complexity: "The cart component at components/Cart.tsx has 6 interactive states — each needs updating"]
  • [State management: "This requires a new Redux slice and cache invalidation across 3 existing slices"]
  • [Design system gap: "The date picker component doesn't exist — must be built, not assembled"]
  • [Accessibility: "No ARIA patterns established in this area — will need to establish from scratch"]

Confidence: HIGH / MEDIUM / LOW (If LOW: state specifically what is unknown)


QA Engineer

Domain: Test surface, edge cases, E2E coverage, regression risk, test infrastructure.

Files read: [list of test files reviewed]

Estimate: [X points or ?]

Justification:

  • [Coverage gaps: "No unit tests for the discount calculation logic — 100% of this path needs new tests"]
  • [E2E gap: "The checkout flow has no E2E tests — adding this feature requires establishing that coverage"]
  • [Regression risk: "Changes to utils/pricing.ts affect 8 downstream consumers — regression suite must be extended"]
  • [Edge cases to cover: list the specific edge cases requiring explicit test scenarios]

Risk flags:

  • Missing coverage in critical user path
  • No E2E tests for this user-facing flow
  • High regression risk in [area]: [reason]
  • Flaky tests in affected area (adds verification overhead)

Confidence: HIGH / MEDIUM / LOW


DevOps Engineer

Domain: Deployment complexity, infrastructure changes, CI/CD, feature flags, monitoring, rollback strategy.

Files read: [list of config/infra files reviewed]

Estimate: [X points or ?]

Justification:

  • [Deployment complexity: "This migration alters a column type — requires a maintenance window or multi-step deploy"]
  • [Infra changes: "Two new environment variables needed across 3 environments — secrets rotation required"]
  • [Observability gap: "No metrics or alerts for this flow — adding monitoring is required, not optional"]
  • [Feature flag: "The rollout risk warrants a feature flag — flag setup and cleanup are in-scope"]

Deployment assessment:

  • Zero-downtime deployment: YES / NO / UNCERTAIN
  • Rollback strategy: [describe specifically — "revert migration" is not a rollback strategy]
  • Feature flag recommended: YES / NO — [rationale]
  • Monitoring/alerting required: [describe gaps that are in-scope for this work]

Risk level: LOW / MEDIUM / HIGH Confidence: HIGH / MEDIUM / LOW


Step 3 — Divergence check

Compare the four estimates.

If any two estimates differ by 2x or more:

Open a discussion round:

Discussion Round

Diverging estimates: [Persona A: X points] vs [Persona B: Y points]

What Persona A sees that Persona B doesn't: [Specific technical reason — reference code]

What Persona B sees that Persona A doesn't: [Specific technical reason — reference code]

Resolution:

  • Read more code to resolve the disagreement
  • Acknowledge that the uncertainty is genuine → both personas adjust to ? or align on a range
  • Agree the scope is different between personas (e.g., QA is estimating test work that Backend didn't account for)

After discussion, each persona may revise their estimate. Show revised estimates.


Step 4 — Consensus

Summary

PersonaEstimateConfidenceKey risk
BackendXHIGH/MED/LOW[one-line]
FrontendXHIGH/MED/LOW[one-line]
QAXHIGH/MED/LOW[one-line]
DevOpsXHIGH/MED/LOW[one-line]

Consensus estimate: [X points] (Method: average / weighted by confidence / adjusted after discussion — explain the choice)

Total effort signal: [Backend + Frontend + QA + DevOps = Y total points across disciplines] (This is a cross-discipline signal, not a single-engineer number)

Recommendation

READY TO SCHEDULE — All personas confident, no unresolved spikes. Proceed to sprint planning.

or

NEEDS SPIKE — [Area] carries too much uncertainty. Spike first:

  • Spike goal: [what must be learned]
  • Timebox: [1–3 days]
  • Spike output: [what the spike should produce — a decision, a proof of concept, a measured data point]
  • Re-estimate after spike.

or

NEEDS SPLITTING — Estimate exceeds 13 points. Run /story to decompose into smaller units, then re-estimate each story.

Top risks to monitor

  1. [Most significant risk from any persona — specific and actionable]
  2. [Second most significant]
  3. [Third, if applicable]

Save artifact

After producing the complete estimation, save it to the project:

  1. Create docs/estimates/ if it doesn't exist.
  2. Derive a kebab-case slug from the story or feature name (e.g. "Add payment method" → add-payment-method).
  3. Write the full output to: docs/estimates/YYYY-MM-DD-{slug}.md using today's actual date.
  4. Tell the user the exact path where it was saved.

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.