Estimate development effort using affected code, design documents, dependencies, and past sprint results. Get optimistic, expected, and pessimistic day estimates, along with a confidence level, key risks, and a suggested breakdown into smaller tasks.
Estimating effort before starting a feature
Planning changes that span several systems
Assessing uncertainty when sprint history is missing
Donchitos/Claude-Code-Game-Studios☆ 27KUpdated Oct 19, 2026
Check whether a game project is ready for its next development phase. Review required documents, test evidence, and quality criteria, then receive a readiness verdict with blockers, missing materials, and any checks that could not be completed.
Checking readiness to begin production
Reviewing missing materials before release
Assessing a phase transition against project quality settings
Donchitos/Claude-Code-Game-Studios☆ 27KUpdated Oct 19, 2026