Agent skills by donchitos

Validate a UX spec, HUD design or pattern library — accessibility, GDD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.

Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After GDDs, architecture, UX specs.

Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike /project-stage-detect, checks compliance not existence.

Create an ADR documenting a technical decision: context, alternatives considered, consequences.

Traceability matrix mapping GDD requirements to ADRs. Finds gaps, cross-ADR conflicts, engine compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Per-asset visual specs plus AI generation prompts from GDDs and character profiles. After the art bible.

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

Guided concept ideation using professional studio techniques, player psychology, creative exploration.

Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

Architectural code review — coding standards, SOLID, testability, performance concerns.

Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.

Audit GDD content counts against what's implemented — planned vs built.

Author the architecture blueprint before code is written. Validates decisions against the pinned engine, flags knowledge gaps.

Flat must-do/never-do rules sheet per system and layer, extracted from Accepted ADRs. ADRs explain why; this is actionable.

Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug].

Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.

Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

Section-by-section GDD authoring for one system — walks through each required section, cross-references dependencies.

Implement a story: ADR guidelines, right programmer agent, code plus test. Then /story-done (/story-readiness before, /code-review after, at standard/full).