스킬 찾기

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

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.

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

• Finding the next task after a development milestone
• Resuming work from the previous session
• Checking which unfinished task needs attention first

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.

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

• Checking consistency after adding a game design document
• Finding conflicting item prices or attributes
• Reviewing documents changed since the last review

Review a game design document before implementation. Check missing sections, conflicting rules, formulas, dependencies, and testable success conditions, then report blocking issues and recommended changes. Full mode adds reviews by relevant specialist agents.

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

• Check a design document before implementation
• Find formula errors and conflicting system rules
• Rewrite vague success conditions as measurable checks

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.

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

• Reviewing completed work at the end of a sprint
• Investigating estimation gaps and carried-over tasks
• Checking progress on previous improvement actions

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

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

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

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.

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

• Reviewing game code before closing a development task
• Checking implementation against recorded architecture decisions
• Finding testability gaps and performance concerns

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

Turn game bug descriptions or suspected code problems into structured reports with reproduction steps, severity, and priority. Follow reported bugs through fix verification and closure, recording test results or manual checks before marking an issue closed.

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

• Turning a bug description into a structured report
• Finding potential bugs in a specific file
• Verifying a fix through tests or manual checks

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.

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

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

Turn accepted architecture decisions, project preferences, and engine references into a practical rules document. Organize required patterns, forbidden approaches, and performance limits by architectural layer, with a source attached to each rule.

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

• Consolidating implementation rules from accepted decisions
• Updating rules after architecture decisions change
• Reviewing naming conventions and performance limits

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.

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

• Understanding the state of an inherited game project
• Getting oriented when joining a development team
• Checking gaps before a milestone

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

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

Turn game design and architecture documents into epics, bounded groups of development work for individual modules. Produce scope documents and an index, showing which requirements have recorded design decisions and where guidance is missing.

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

• Turning game designs into module-level development scope
• Planning epics for a specific development layer
• Finding requirements without architecture decisions

Prepare a game's launch day patch by selecting known bugs that are safe to fix quickly. Coordinate minimal fixes, verify affected areas, and document deferred issues, quality checks, rollback procedures, and patch notes.

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

• Selecting known bugs for a launch day patch
• Planning minor fixes from platform certification feedback
• Verifying fixes and checking affected game systems

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

Build a game launch checklist covering code, content, quality, stores, legal preparation, infrastructure, marketing, and operations. Tailor checks to the project's stage and release requirements, then summarize blockers, accepted risks, missing confirmations, and required sign-offs.

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

• Reviewing launch readiness across departments
• Preparing checks for itch.io, Steam, or console releases
• Separating launch blockers from unassessed items

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.

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

• Preparing a playtest report template
• Organizing raw playtest notes
• Separating gameplay issues from bugs

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 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.

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

• Documenting a feature built without a design document
• Understanding an inherited codebase with missing documentation
• Turning a gameplay prototype into a concept document