Skill rating

New or updated sprint plan from the current milestone, completed work, and available capacity.

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.

Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish. Uses /ux-design, /ux-review, studio templates.

Security audit — save tampering, cheat vectors, network exploits, data exposure, input validation. Before public or multiplayer release.

Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After GDDs, architecture, UX specs.

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

View or change project config — effective merged values, or set locally in project.local.yaml.

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

Orchestrate the audio team — audio-director, sound-designer, technical-artist, gameplay-programmer — direction through implementation.

Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

Audit GDD content counts against what's implemented — planned vs built.

Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.

Decompose a concept into individual systems, map dependencies, prioritize design order, create the systems index.

Localization pipeline — find hardcoded strings, extract string tables, cultural review, VO, RTL, enforce string freeze.