Estimate
Estimation workflow for a feature or task. Breaks the task into sub-tasks, estimates each, sums with contingency buffer.
Install
$ agentstack add skill-codephobiia-claude-roblox-game-studio-estimate ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-codephobiia-claude-roblox-game-studio-estimate) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
/estimate — Task Estimation
Delegate to: producer (with lead-programmer for tech estimates)
Steps
1. Gather Context
Ask: "What task / feature do you want to estimate?"
2. Break Down Into Sub-Tasks
For a typical feature, list:
- Design: GDD writing (0.5-2 days)
- Implementation: Code writing (1-10 days depending on scope)
- Art assets: If needed (varies wildly)
- Integration: Hooking into existing systems (0.5-2 days)
- Testing: QA plan + execution (0.5-2 days)
- Polish: Rough edges, edge cases (0.5-1 day)
- Review: Code review, design review (0.5 day)
3. Estimate Each Sub-Task
Use T-shirt sizing for unclear items, hours for clear items:
- XS: 40% of sprint capacity (single task dominating the sprint)
- Flag if total breakdown doesn't match vague intuition
6. Present Estimate
# Estimate: [Feature Name]
## Sub-tasks
| Task | Size | Hours (est) | Risk |
|------|------|-------------|------|
| Design GDD | S | 6 | Low |
| Implement core | M | 16 | Medium |
| Implement UI | S | 8 | Low |
| Test + polish | S | 6 | Low |
| Review + iterate | S | 4 | Low |
**Subtotal**: 40 hours
**Contingency** (30%): 12 hours
**Total estimate**: ~52 hours (~6.5 working days)
## Risks
1. [Risk 1 — how it affects estimate]
2. [Risk 2]
## Assumptions
- [Assumption 1]
- [Assumption 2]
## Dependencies
- [Other tasks/systems this depends on]Output
Present estimate to user. If too large, suggest splitting the feature. Save estimates to production/sprints/estimates/ when approved.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CodePhobiia
- Source: CodePhobiia/claude-roblox-game-studio
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.