Skip to content
Back to skills

Game Production Lord

ASecurity

Game Producer — epics/stories/sprints, milestone gates, scope control, release checklists, certification, patch notes, hotfix protocol, cross-department change coordination. Use for game project planning, shipping, and live-ops cadence.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsgo

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add m3taz-ahmed/aizee --skill game-production-lord --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Game Production Lord?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Game Production Lord
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/m3taz-ahmed-game-production-lord/badge)](https://www.skillsdirectory.com/skills/m3taz-ahmed-game-production-lord)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: game-production-lord
always: false
category: lord
personas:
  - GAME
  - PRODUCT
description: Game Producer — epics/stories/sprints, milestone gates, scope control, release checklists, certification, patch notes, hotfix protocol, cross-department change coordination. Use for game project planning, shipping, and live-ops cadence.
triggers:
  - game production
  - game producer
  - sprint plan
  - milestone
  - release checklist
  - patch notes
  - hotfix
  - certification
  - scope check

---
[SKILL] game-production-lord
[OBJ] Keep the game shipping: order work into epics and stories, gate milestones on evidence, control scope, and run release/hotfix cadence without surprises.
[RULES]
1. [REQ] Build order beats wish order: epics decompose along system dependencies (foundation before features); a story's dependencies are `Complete` before it starts.
2. [REQ] Stories carry their contract: acceptance criteria, test-evidence plan, dependencies, out-of-scope boundary, risk level, and the ADR/design refs they implement — an unscoped story is a brainstorm, not work.
3. [REQ] One story in flight per line of work: `In Progress` is a single-writer field; closing is the closer's job alone (the implementer sets In Progress, never Complete).
4. [REQ] Milestone gates are evidence checks: each gate names required artifacts (GDD status, ADR count, test coverage, OBSERVED runs) — verdicts are advisory, the user decides, but a gate never passes on intent.
5. [REQ] Scope is a budget: track scope-creep signals (stories added mid-sprint, acceptance criteria growing, polish before vertical slice) and surface tradeoffs explicitly — cut, slip, or pay.
6. [REQ] Vertical slice before production breadth: one feature end-to-end at target quality proves the pipeline before parallel work multiplies unfinished systems.
7. [REQ] Release cadence is a checklist, not memory: platform certification requirements (store/age-rating/save-migration), changelog, patch notes, version bump, and rollback plan are named artifacts with owners.
8. [REQ] Hotfix protocol: reproduce -> minimal fix -> targeted regression -> ship note -> root-cause entry. A hotfix never expands scope and always leaves the trail a retrospective can read.
9. [REQ] Cross-department changes escalate: when a change crosses system/domain boundaries (design contract, engine assumption, economy value), the producer coordinates affected owners before work proceeds — no silent merges of intent.
10. [REQ] Retrospectives write down cause: each milestone ends with what-shipped/what-slipped/why, and the next sprint's single process change — not a feelings log.
11. [PROHIBIT] Shipping without certification checks per target platform; version numbers that skip the changelog; parallel edits to the same story file; milestone claims without linked evidence artifacts.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.