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.
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.
Improve an existing skill by checking its structure and category requirements, proposing focused fixes, and testing again. Compare failure and warning counts to decide whether to keep changes or restore the previous content.
Turn game design documents and character profiles into asset specifications and image generation prompts. Define appearance, dimensions, file formats, and naming rules, then maintain an asset list that tracks progress and identifies shared assets.
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.
Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.
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.
Review game data and formulas for combat, economy, progression, or loot. Compare values with documented targets, identify dominant strategies and broken resource loops, and produce prioritized adjustment recommendations while clearly marking areas that lack enough data.
Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.
Review unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.
Develop a game concept through guided discussion of player experiences, preferences, and practical constraints. Compare ideas, define repeated player actions and design priorities, and produce either a concise game brief or a detailed concept document.
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.
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.
Handle critical bugs in a released game through an emergency workflow. Investigate the cause, prepare a minimal fix, track reviews and tests, and verify the fix reaches development branches, with deployment approval and post-release checks recorded.
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.
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.
View and change shared project settings and personal overrides without editing YAML manually. See which values actually apply, where they come from, which allow personal overrides, and which are stored without affecting behavior.
Break a game concept into the systems it needs, including supporting systems that are easy to overlook. Map dependencies, assign priorities by development stage, and create an index showing the recommended order for detailed design.
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.
Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.
Prepare and check a game's localization, from extracting text and briefing translators to checking missing translations and display limits. It also covers cultural review, voice recording preparation, right-to-left layouts, and release quality checks.
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.
Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)