governing-game-user-research-coverage

Audits and plans Games User Research coverage across eleven evidence domains.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill governing-game-user-research-coverage-alsdmlals4-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governing-game-user-research-coverage
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/governing-game-user-research-coverage
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill governing-game-user-research-coverage-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects often either skip user research entirely or inflate research activity without tying it to real development decisions. This Skill installs a structured coverage model that anchors every research effort to a specific decision it should change, while tracking gaps across eleven evidence domains. ## Core Features & Use Cases - Decision-first research framing: Fixes the research question, the decision to change, evidence needed, and evidence ceiling before any study begins. - Eleven-domain coverage audit: Tracks market analysis, benchmarking, SWOT, user research, playtests, tutorial comprehension, UX issues, telemetry, balance data, experiments, and improvement decisions with explicit status values like NOT_STARTED, NOT_APPLICABLE, and VERIFIED. - Project-declared validation policy: Supports machine-primary acceptance routes without forcing a universal participant count or mandatory human-study sequence on every project. - Use Case: A game team preparing a vertical slice uses the audit mode to discover that telemetry and tutorial comprehension domains are NOT_STARTED while market analysis is over-documented, then reprioritizes playtest and instrumentation work accordingly. ## Quick Start Audit my game project's user research coverage across the eleven domains and produce a coverage matrix with priorities for the next playtest.

Frequently Asked Questions about governing-game-user-research-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit user research coverage for a game project?

Run the audit mode to map all eleven evidence domains, from market analysis to improvement decisions, against their current status. Each domain is marked NOT_STARTED, IN_PROGRESS, VERIFIED, or NOT_APPLICABLE with a recorded reason, producing a coverage matrix and prioritized next steps.

What are the eleven Games User Research domains?

The domains are market and genre analysis, competitor benchmarking, SWOT positioning, user research, playtesting, tutorial comprehension, UX problem analysis, telemetry and funnels, balance data, hypothesis experiments, and improvement decisions with adoption rationale.

Does this framework require playtests with a fixed number of participants?

No. It uses a project-declared validation policy, so machine-primary evidence can be the main acceptance route and human studies are recorded only when the project or user requests them. It never imposes a universal participant count or mandatory study sequence.

When should a research domain be marked NOT_APPLICABLE?

Mark a domain NOT_APPLICABLE when it cannot affect the current decision, risk, or player promise, and record the reason. The goal is decision-relevant coverage, not filling all eleven domains, so 11/11 completion is explicitly not the success condition.

What are the limitations of this research coverage approach?

It governs structure and evidence planning only; it does not execute concept analysis, playtest interpretation, document generation, or instrumentation itself. Those tasks belong to separate skills and project contracts, so this Skill never duplicates actual research execution.