74 skills (repositories by Donchitos) · sorted by popularity
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.