스킬 찾기

Review test files and manual verification records for development tasks. Check whether expected behavior, edge cases, screenshots, and required approvals are covered, then report evidence gaps and distinguish completion blockers from advisory improvements.

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

• Reviewing test evidence for a single development task
• Auditing evidence across a sprint or system
• Checking screenshots and required visual approvals

Find and organize technical debt, the code issues deferred for later improvement. Maintain a register, rank items by impact and repair effort, and report unresolved work and changes over each sprint.

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

• Scan code for signs of deferred maintenance
• Record known issues and reasons for deferring fixes
• Prioritize fixes by impact and effort

Review a completed development task against its acceptance criteria, check differences from design and architecture documents, and prompt code review. After approval, update the task's status and identify the next story to work on.

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

• Checking acceptance criteria before closing a development task
• Recording differences between implementation and design
• Remembering code review before marking work complete

Coordinate a game interface feature from user experience specifications through visual design, implementation, review, and polish. Reuse existing interaction patterns and report input support, accessibility checks, engine validation, and unresolved issues alongside the delivered interface.

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

• Building an inventory screen from specification through implementation
• Designing and implementing a game's main menu
• Creating a HUD with defined visual and interaction constraints

Set up automated testing before implementation begins. Detect the configured game engine, create test folders and runner configuration, and prepare a GitHub Actions workflow so tests can run automatically on each push.

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

• Set up automated testing before the first sprint
• Create test folders and runner configuration
• Prepare GitHub Actions to run tests on each push

Coordinate game area design from story, world context, and visual direction through layout, enemies, rewards, accessibility, and test planning. Compile the results into a level design document, with specialist participation determined by the configured team size.

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

• Designing a tutorial village or dungeon
• Aligning area layouts with story and visual direction
• Planning enemy encounters and reward placement

Prepare a long play session with timed observation checkpoints and logs for memory growth, stability, and player fatigue. It creates the testing protocol and analysis template; a human plays the game and records the findings.

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

• Prepare an endurance test before release
• Check for recurring memory issues after a fix
• Track crashes and performance over a long session

Create or update a sprint plan, a short development work plan, using existing work items, completed work, and available capacity. Organize priorities, carryover, dependencies, and risks, and produce a progress report.

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

• Plan the next sprint around available capacity
• Re-estimate unfinished work carried into the next sprint
• Update task priorities and estimates

Coordinate game audio work from creative direction through sound specifications, accessibility requirements, technical planning, and code integration. Combine the participating agents’ outputs into an audio design document for a chosen feature or area.

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

• Planning combat sound effects and gameplay triggers
• Designing ambience for a forest area
• Planning adaptive music for a boss encounter

Refine a game feature or area through performance measurement, visual and audio polish, and stress and regression testing. Report before-and-after metrics, remaining issues, and release readiness, with work limited to the enabled team roles.

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

• Identify performance bottlenecks in combat
• Refine particle effects and shaders
• Review sound feedback and audio mixing

Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.

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

• Planning QA for a sprint or game feature
• Preparing manual test cases from acceptance criteria
• Recording test results, bugs, and screenshot evidence

Analyze repeated CI test runs to find tests that pass and fail without code changes. Summarize failure rates, investigate likely causes, and recommend fixes, monitoring, or temporary exclusion based on the available evidence.

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

• Investigating intermittent CI test failures
• Comparing failure rates across repeated test runs
• Reviewing tests already marked for temporary exclusion

Check a game build before handing it to QA, the team responsible for quality checks. Run automated tests, review coverage gaps, confirm critical paths with the developer, and produce a report with results and unresolved checks.

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

• Checking a build before QA hand-off
• Rechecking a build after fixing a failure
• Reviewing platform-specific controls and behavior

Check whether development tasks are ready for implementation by reviewing acceptance criteria, design decisions, dependencies, and required evidence. Receive one of four verdicts for each task, with specific gaps and suggested fixes.

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

• Checking a task before assigning implementation
• Reviewing all tasks in the current sprint
• Finding ambiguous acceptance criteria

Coordinate role-based agents to design, implement, integrate, and test a game combat feature. The workflow covers gameplay rules, enemy behavior, visual effects, and audio planning, with a final report on completion, test results, and unresolved issues.

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

• Design and implement a parry mechanic
• Coordinate enemy reactions, effects, and audio events
• Review combat architecture for the configured engine

Coordinate a game release from candidate preparation through testing, release approval, and deployment. Assign work to role-based agents and collect quality results, patch notes, launch messaging, and a post-release monitoring plan.

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

• Prepare a release candidate and checklist
• Collect testing and release readiness results
• Decide whether a release should proceed

Review game interface specifications, HUD designs for information shown during play, and shared interaction rules before implementation. Check completeness, accessibility, and consistency with game design documents, then receive a verdict with specific issues and missing review inputs.

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

• Checking a screen specification before implementation
• Reviewing HUD information and display priorities
• Checking consistency across shared interaction patterns

Build a short, playable game sequence before full production to check whether the complete gameplay loop works at the intended quality. Use playtest observations and daily progress records to assess feasibility and decide the next direction.

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

• Checking production feasibility after game design is complete
• Testing a complete gameplay loop with players
• Estimating production speed from actual build progress

Write game interface specifications for individual screens, interaction flows, and the HUD, the information shown during play. Also document shared interaction patterns and project-wide accessibility requirements, with section depth guided by project settings.

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

• Writing specifications for game screens and navigation flows
• Designing the HUD information shown during play
• Documenting shared interaction patterns

Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.

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

• Create a base library of test helpers
• Share repeated test setup and result checks
• Generate object factories for a specific game system

Get started with a game project by reviewing existing work and answering questions about the idea, project scope, and preferred confirmation frequency. Save initial project settings and receive a workflow matched to the chosen level of process.

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

• Starting a game project without an idea
• Choosing next steps for a rough or clear concept
• Organizing existing game documents and code

Plan a game season or limited-time event across content, story, rewards, pricing, measurement, and player communication. Coordinate role-based agents to produce a season design, analytics plan, and communication calendar for production.

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

• Plan a game season or limited-time event
• Design reward tracks and seasonal currency pricing
• Define success metrics and A/B tests

Plan game stories, world lore, dialogue, visual direction, and story placement within levels through a staged workflow. Produce narrative documents with consistency checks and localization considerations, using the roles enabled by the team settings.

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

• Draft dialogue for a boss encounter
• Develop lore for factions and locations
• Place story discoveries within a level

Read sprint plans and work records to summarize completion, remaining time, blocked tasks, and emerging risks. Compare progress with elapsed time, flag stale work, and provide a concise status report with at most one recommended action.

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

• Get a quick snapshot of the current sprint
• Spot stalled work and blockers
• Check whether required work is at risk