Review a development milestone using sprint reports, feature status, bugs, and risks. Summarize completion, quality, and delivery pace, then recommend whether to proceed, proceed with conditions, or stop, with scope choices and action items.
Review game code for likely performance bottlenecks in processing, memory, rendering, and data loading. Compare available estimates with configured limits and produce ranked optimization recommendations, including expected impact, effort, risks, and areas needing runtime measurement.
Create a game playtest report template or turn session notes into organized feedback. Separate gameplay problems from bugs, compare observations with design intent, and identify priorities for design changes, balance adjustments, and polish.
Trace changes in a game design document to related architecture decision records, which explain technical choices. Compare their assumptions with the revised design, report which decisions need review, and guide updates to decisions and requirement links.
Create a game development test plan for a sprint, feature, or individual task. Classify the work and specify automated tests, manual checks, basic functionality checks, and playtest needs from documented requirements.
Turn small game changes into concise specifications with clear reasons, rules, and acceptance criteria. Check existing design documents and earlier specifications, then document tuning adjustments, minor behavior changes, or small features before implementation.
Create a game release checklist tailored to target devices and distribution requirements. Review builds, bugs, store information, and launch preparations, then report readiness while clearly separating known blockers from checks that could not be assessed.
Review a sprint or milestone by comparing planned work with actual results. Summarize completion, estimation gaps, and blockers, then produce a retrospective with specific improvement actions, owners, and deadlines for the next iteration.
Review multiple game design documents together to find conflicting rules, overlapping responsibilities, economic imbalance, and strategies that overshadow others. Assess how systems interact and identify issues that individual document reviews can miss.
Compare a feature, sprint, or milestone with its original plan to identify scope creep, meaning unplanned growth in work. Quantify additions and removals, assess delivery risks, and recommend what to cut, defer, or keep.
Audit game code for save tampering, cheating, network weaknesses, input validation gaps, exposed data, and dependency risks. Produce a report with severity ratings, repair priorities, release recommendations, and explicit notes about areas that could not be assessed.
Review skill and agent definitions for structural issues and whether their instructions meet expected behavior. Four modes cover structure, test specifications, category criteria, and coverage reports that reveal missing specifications or checks.
Turn Git commits and sprint records into internal and player-facing game changelogs. Group related features, fixes, and balance changes, retain technical references for the team, and describe player-visible changes in clear language.
Find the next step in a game development project by checking workflow records, existing documents, and task status. Get one main recommendation with a command, plus a brief view of completed work and upcoming tasks.
Create a game's art direction document, defining its visual rules, mood, shapes, colors, and production standards. Review and approve sections individually, with guidance that connects character, environment, and interface design to the game's concept and technical constraints.
Review game code for architecture, coding standards, testability, and performance concerns. Get findings tied to specific code, checks against recorded design decisions, and a report separating required fixes from optional improvements.
Check game design documents against a shared registry of entities, items, formulas, and constants. Get a report of conflicting values, outdated registry entries, and references that lack enough detail to verify, with guidance on which documents need changes.
Compare planned game content counts with implementation files for enemies, levels, items, abilities, dialogue, and quests. Produce a gap table showing approximate progress and priority shortages, either across all systems or for one selected system.
Write a game design document for one system, such as combat, crafting, or dialogue. Work through sections with specialist agent input, check dependencies against existing designs, and save approved sections with progress records for later continuation.
Create an onboarding document for a new contributor or agent, tailored to their role. Gather project context, relevant conventions, key files, current work, and suggested first tasks into a practical starting guide.
Assess a game project's development stage by examining design documents, code, tests, and planning files. Identify gaps appropriate to its workflow, compare findings with the configured stage, and recommend next steps for different team roles.
Build a quick, disposable game prototype in HTML, a game engine, or on paper to test one core mechanic. Use playtest findings to decide whether to continue, change direction, stop, or leave the idea unassessed.
Turn existing game code or prototypes into missing design, architecture, or concept documents. Extract implemented rules, formulas, and technical choices, ask about their intended purpose, and clearly separate observed behavior from unconfirmed interpretations.
Choose a game engine and version, record the choice in project configuration, and prepare reference documents for newer releases. The skill also supports refreshing those references and guiding migration between engine versions.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)