# Gsp Mechanics Systems Audit

> Use when auditing core verbs, loop integrity, progression, or whether implemented systems form a playable game.

- Skill: `mike007jd/gsp-mechanics-systems-audit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mike007jd/gsp-mechanics-systems-audit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mike007jd/gsp-mechanics-systems-audit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: mike007jd (https://skillmd.com/u/mike007jd)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mike007jd/gsp-mechanics-systems-audit

---


# Game Mechanics Systems Audit

## Goal
Audit whether the project’s systems compose into a coherent game rather than a pile of disconnected features.

## Outputs

Follow the `gsp-orchestrator` output strategy:
- **inline** (default): present findings in conversation.
- **minimal** or **full**: write to `docs/game-studio/audit/audit-summary.md`, `docs/game-studio/audit/scorecard.json`, `docs/game-studio/audit/repair-roadmap.md`.

Use:
- `../../shared/checklists/mechanics-systems-audit-checklist.md`
- `../../shared/reference/game-dev-abstractions.md`
- `../../shared/reference/audit-confidence-and-evidence.md`

## Evaluate
- clarity of the primary verb
- reward loop and fail loop integrity
- progression, encounter, economy, or puzzle logic cohesion
- whether systems conflict or duplicate responsibility
- whether important features are present only as shells

## Output style
Prefer statements like:
- “the combat loop is under-closed because…”
- “progression exists structurally but not experientially because…”
- “feature count is high, but loop cohesion is low because…”