Donchitos

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a combat or crafting system design
• Checking dependencies against existing game designs
• Developing specifications with specialist agent input

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a guide for a new programmer
• Orienting designers or narrative contributors
• Sharing current work with QA or production staff

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test whether a core game mechanic is fun
• Compare several variations of a game concept
• Explore a mechanic change during production

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• List the visual assets needed for a game
• Define consistent character and environment asset specifications
• Prepare image generation prompts from an art direction guide

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a feature has grown beyond its plan
• Measuring scope changes during a sprint
• Choosing additions to cut or defer

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking effective settings and their sources
• Changing settings shared by the team
• Applying personal overrides

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting game balance adjustments
• Specifying minor behavior changes
• Defining a small mechanic for an existing system

Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

Audit an existing project's design documents and supporting files to check whether their formats work with the template's skills. Get a numbered migration plan that prioritizes gaps and required changes, rather than simply listing what exists.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking existing documents before adopting a project template
• Auditing game design documents or architecture decision records
• Prioritizing gaps in project tracking and configuration files

Turn game changelogs and Git history into patch notes that explain what players will experience. Organize new content, balance changes, fixes, and known issues in accessible language, while excluding internal maintenance work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting player-facing notes for a game update
• Explaining balance changes with before-and-after values
• Matching patch notes to an existing tone guide

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a changelog for a game version
• Summarizing changes completed during a sprint
• Writing an internal record with commit references

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix missing fields and instructions in a skill
• Address findings from category checks
• Compare check results before and after edits

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing planned and implemented game content
• Finding shortages in priority features
• Auditing content for a single game 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing weapon damage and combat effectiveness
• Finding resource loops and pricing problems
• Reviewing experience and power progression

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing open bugs at the start of a sprint
• Organizing new bugs after a team QA review
• Reviewing a backlog with more than ten open bugs

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring game ideas from a genre or theme
• Turning a vague idea into a repeatable play cycle
• Defining a minimum playable version and development boundaries

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking architecture impact after changing game design
• Finding technical decisions based on outdated requirements
• Choosing whether to keep, revise, or replace a decision

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding performance bottleneck candidates in one game system
• Reviewing performance across the whole game
• Comparing available estimates with configured performance limits

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Responding to crashes or data loss in a released game
• Preparing a minimal emergency patch
• Tracking patch approvals, tests, and rollback plans

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking consistency across game system design documents
• Assessing overall balance after major design changes
• Finding cross-system problems before architecture work

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing progress before a milestone deadline
• Identifying blockers and quality risks
• Choosing features to protect or defer

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identifying the systems a game concept requires
• Finding dependency cycles and bottleneck systems
• Choosing systems for the minimum playable version