GitHub Project Management Swarm
ruvnet/agentic-flow
Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.
Estimates the effort for a game development task from code complexity, scope, risk and past sprint data, returning a range with a confidence level.
Install Task Effort Estimator
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/estimate .claude/skills/estimate && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .claude/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/estimate .agents/skills/estimate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .agents/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/estimate .cursor/skills/estimate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .cursor/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Donchitos/Claude-Code-Game-Studios.git --path .claude/skills/estimate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/estimate .gemini/skills/estimate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .gemini/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/estimate .github/skills/estimate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .github/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios estimate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/estimate .opencode/skills/estimate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "estimate" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate into .opencode/skills/estimate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "estimate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
estimate- GitHub stars
- 26k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 384 words
- Files
- 1
- Skills in repo
- 73
- Repo updated
- First seen
- Licence
- MIT
At a glance
Estimates the effort for a game development task from code complexity, scope, risk and past sprint data, returning a range with a confidence level.
- Works in 5 steps: Understand the Task → Scan Affected Code → Analyze Complexity Factors → …
- Sizing a gameplay or engine task before adding it to a sprint
- SKILL.md covers Phase 1: Understand the Task, Phase 2: Scan Affected Code, Phase 3: Analyze Complexity… and Phase 4: Generate the Estimate, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The skill runs a read-only, five-phase pass to size a task. It reads the task description from the argument, then project context in CLAUDE.md and any matching design documents under `design/gdd/`, asking for clarification when the request is too vague to estimate. Next it scans the code that would change, looking at size, dependency count, integration points and existing test coverage, and reads past sprint data in `production/sprints/` for comparable work.
It then weighs code complexity, scope and risk, including new technology, unclear requirements, unfinished dependencies and performance sensitivity, and writes a structured estimate with optimistic, expected and pessimistic figures, a recommended budget equal to the expected case, a confidence level and the single biggest risk. With no sprint history it says so and treats the missing calibration as a risk instead of padding numbers. Low confidence leads to a suggested time-boxed prototype, and tasks over 10 days to a suggestion to split them into stories.
When your agent uses it
- Sizing a gameplay or engine task before adding it to a sprint
- Deciding whether a vague feature needs a prototype spike first
- Producing a range estimate with a stated confidence level for a producer
- Checking if a task is too large and should be split into stories
Example prompts
- “Estimate adding a dodge-roll ability to the player controller.”
- “How long would moving the save system to a new file format take, with a confidence level.”
- “Give me an optimistic, expected and pessimistic estimate for the inventory UI rework.”
- “Estimate the work to port the enemy AI to the new behavior tree system.”
Requirements
- A project with CLAUDE.md; sprint history in `production/sprints/` improves calibration
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b21fa0f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Task Effort Estimator loads about 1.2k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 384 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Donchitos/Claude-Code-Game-Studios at commit b21fa0f, republished under its MIT licence (© Donchitos). 384 words, ~1,151 tokens.
Download SKILL.mdSave it as
.claude/skills/estimate/SKILL.md (or your agent's skills folder).- name
- estimate
- description
- Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.
- allowed-tools
- Read, Glob, Grep
- argument-hint
- [task-description]
- user-invocable
- true
- model
- sonnet
Phase 1: Understand the Task
Read the task description from the argument. If the description is too vague to estimate meaningfully, ask for clarification before proceeding.
Read CLAUDE.md for project context: tech stack, coding standards, architectural patterns, and any estimation guidelines.
Read relevant design documents from design/gdd/ if the task relates to a documented feature or system.
Phase 2: Scan Affected Code
Identify files and modules that would need to change:
- Assess complexity (size, dependency count, cyclomatic complexity)
- Identify integration points with other systems
- Check for existing test coverage in the affected areas
- Read past sprint data from
production/sprints/for similar completed tasks and historical velocity. If there is none, say so under Notes and Assumptions — "No sprint history found; this estimate is not calibrated to the team's velocity" — and treat that as a risk in the confidence level, not as a silent padding of the figures.
Phase 3: Analyze Complexity Factors
Code Complexity:
- Lines of code in affected files
- Number of dependencies and coupling level
- Whether this touches core/engine code vs leaf/feature code
- Whether existing patterns can be followed or new patterns are needed
Scope:
- Number of systems touched
- New code vs modification of existing code
- Amount of new test coverage required
- Data migration or configuration changes needed
Risk:
- New technology or unfamiliar libraries
- Unclear or ambiguous requirements
- Dependencies on unfinished work
- Cross-system integration complexity
- Performance sensitivity
Show full SKILL.md (156 more words)Show less
Phase 4: Generate the Estimate
## Task Estimate: [Task Name]
Generated: [Date]
### Task Description
[Restate the task clearly in 1-2 sentences]
### Complexity Assessment
| Factor | Assessment | Notes |
|--------|-----------|-------|
| Systems affected | [List] | [Core, gameplay, UI, etc.] |
| Files likely modified | [Count] | [Key files listed below] |
| New code vs modification | [Ratio] | |
| Integration points | [Count] | [Which systems interact] |
| Test coverage needed | [Low / Medium / High] | |
| Existing patterns available | [Yes / Partial / No] | |
**Key files likely affected:**
- `[path/to/file1]` -- [what changes here]
### Effort Estimate
| Scenario | Days | Assumption |
|----------|------|------------|
| Optimistic | [X] | Everything goes right, no surprises |
| Expected | [Y] | Normal pace, minor issues, one round of review |
| Pessimistic | [Z] | Significant unknowns surface, blocked for a day |
**Recommended budget: [Y days]**
### Confidence: [High / Medium / Low]
[Explain which factors drive the confidence level for this specific task.]
### Risk Factors
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
### Dependencies
| Dependency | Status | Impact if Delayed |
|-----------|--------|-------------------|
### Suggested Breakdown
| # | Sub-task | Estimate | Notes |
|---|----------|----------|-------|
| 1 | [Research / spike] | [X days] | |
| 2 | [Core implementation] | [X days] | |
| 3 | [Testing and validation] | [X days] | |
| | **Total** | **[Y days]** | |
### Notes and Assumptions
- [Key assumption that affects the estimate]
- [Any caveats about scope boundaries]Output the estimate with a brief summary: recommended budget, confidence level, and the single biggest risk factor.
This skill is read-only — no files are written. Verdict: COMPLETE — estimate generated.
Phase 5: Next Steps
- If confidence is Low: recommend a time-boxed spike (
/prototype) before committing. - If the task is > 10 days: recommend breaking it into smaller stories via
/create-stories. - To schedule the task: run
/sprint-plan updateto add it to the next sprint.
Guidelines
- Always give a range (optimistic / expected / pessimistic), never a single number
- The recommended budget should be the expected estimate, not the optimistic one
- Round to half-day increments — estimating in hours implies false precision for tasks longer than a day
- Do not pad estimates silently — call out risk explicitly so the team can decide
- Confidence is Low whenever the approach is undecided or the core requirements are still TBD — a range built on an unmade decision is a guess
© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/estimate of Donchitos/Claude-Code-Game-Studios.
Open the folder on GitHubat commit b21fa0f
Compare with similar skills
Task Effort Estimator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Task Effort Estimator this skillDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.2k | Automated safety check: Pass | MIT | |
| GitHub Project Management Swarmruvnet/agentic-flow | 816 | 6 repos | ~7.1k | Automated safety check: Pass | None | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Project Planneradrianpuiu/claude-skills-marketplace | 100 | 1 repos | ~6k | Automated safety check: Pass | None | |
| Epic Breakdown Advisordeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~6k | Automated safety check: Pass | Custom licence | |
| Bmad Sprint Planningdelorenj/mcp-server-trello | 446 | 5 repos | ~3k | Automated safety check: Pass | MIT |
Similar skills
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
Epic Breakdown Advisor
deanpeters/Product-Manager-Skills
Splits a too-large epic into user stories using Richard Lawrence's nine Humanizing Work splitting patterns while keeping each story a vertical slice of user value.
Bmad Sprint Planning
delorenj/mcp-server-trello
Generate sprint status tracking from epics. An agent skill from delorenj/mcp-server-trello.
Groom Roadmap
talkincode/toughradius
Roadmap and development-plan self-iteration (grooming). An agent skill from talkincode/toughradius.
More from Donchitos/Claude-Code-Game-Studios
All 73 skills in this repoGame Asset Audit
Donchitos/Claude-Code-Game-Studios
Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.
Game Asset Spec Writer
Donchitos/Claude-Code-Game-Studios
Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.
Game Balance Check
Donchitos/Claude-Code-Game-Studios
Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.
Structured Bug Reports
Donchitos/Claude-Code-Game-Studios
Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.
Bug Triage
Donchitos/Claude-Code-Game-Studios
Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.
Changelog Generator for Games
Donchitos/Claude-Code-Game-Studios
Generates an internal or player-facing changelog from git commits and sprint data, filtering out framework maintenance commits so that only work on the game itself reaches release copy.
Related
Questions about Task Effort Estimator
What does Task Effort Estimator do?
Estimates the effort for a game development task from code complexity, scope, risk and past sprint data, returning a range with a confidence level. The skill runs a read-only, five-phase pass to size a task.md and any matching design documents under `design/gdd/`, asking for clarification when the request is too vague to estimate.
When should I use Task Effort Estimator?
Task Effort Estimator fits situations like: sizing a gameplay or engine task before adding it to a sprint; deciding whether a vague feature needs a prototype spike first; producing a range estimate with a stated confidence level for a producer; checking if a task is too large and should be split into stories.
How do I install Task Effort Estimator in Claude Code?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a claude-code`. Or copy the skill folder (.claude/skills/estimate in Donchitos/Claude-Code-Game-Studios) into .claude/skills/estimate in your project. Claude Code loads it when a task matches its description.
How do I install Task Effort Estimator in Codex?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a codex`. Or copy the skill folder (.claude/skills/estimate in Donchitos/Claude-Code-Game-Studios) into .agents/skills/estimate in your project. Codex loads it when a task matches its description.
Can I use Task Effort Estimator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill estimate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/estimate, .gemini/skills/estimate, .github/skills/estimate and .opencode/skills/estimate in your project.
What does Task Effort Estimator need to run?
SKILL.md names no scripts, command-line tools or credentials: Task Effort Estimator is instructions for the agent only. Our summary lists: A project with CLAUDE.md; sprint history in `production/sprints/` improves calibration. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Task Effort Estimator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Task Effort Estimator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Task Effort Estimator use?
Task Effort Estimator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Task Effort Estimator use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Task Effort Estimator?
Skills that share tags, products or a category with Task Effort Estimator: GitHub Project Management Swarm (ruvnet/agentic-flow, 816 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars) and Epic Breakdown Advisor (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Task Effort Estimator?
Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,834 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on September 29, 2026.
Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.