# Gsp Production Feature

> Use when a requested game feature should land as a maintainable product-grade feature, not a prototype slice.

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

---


# Game Production Feature

## Goal
Build or modify a feature so it can live in a serious codebase, not just impress in a quick demo.

## Quality bar
A valid production feature usually includes:
- the requested feature scope,
- clean integration with existing systems,
- production-grade code structure,
- compatibility / migration notes when relevant,
- strong user-facing flow and feedback,
- verification strong enough for continued development.

Use:
- `../../shared/checklists/production-feature-checklist.md`
- `../../shared/checklists/production-code-checklist.md`

## Outputs

Follow the `gsp-orchestrator` output strategy:
- **inline** (default): present quality target updates in conversation.
- **minimal** or **full**: write or update `docs/game-studio/quality-target.md`.

## Workflow
1. Protect the requested feature set.
2. Respect project state and refactor policy.
3. Update quality target (see Outputs).
4. Implement the feature to completion, not as a fake shell.
5. Verify the feature and touched regressions before calling it done.