Skill: mike007jd/game-build-strategy (version 1.0.0)

--- name: game-build-strategy description: Decide the AI-native development mode, quality target, task granularity, and refactor policy based on project state and user intent. This skill prevents both over-cautious iteration and reckless live-product rewrites. license: MIT compatibility: Claude Code and Codex. Best results with file read/write access. metadata: author: game-superpowers version: "1.1.0" domain: game-development --- # Game Build Strategy ## Goal Choose the right build strategy for the project. Write `docs/game-studio/build-strategy.md` and `docs/game-studio/quality-target.md`. Use: - `./shared/reference/development-modes.md` - `./shared/reference/quality-targets.md` - `./shared/templates/build-strategy.md` - `./shared/templates/quality-target.md` ## Development modes - `yolo-super` - `guided-build` - `refactor-open` - `surgical-live` ## Quality targets - `first-playable` - `polished-prototype` - `production-feature` - `live-patch` ## Selection rules - **greenfield + narrow mechanic spike** -> `yolo-super` + `first-playable` - **greenfield + serious showcase build** -> usually `yolo-super` or `guided-build` + `polished-prototype` - **existing product-facing feature work** -> usually `guided-build` or `refactor-open` + `production-feature` - **shipped or live-risky** -> `surgical-live` + `live-patch` ## Planning policy Match task size to the mode: - aggressive modes can use large coherent implementation chunks - production-feature work can use medium coherent chunks - live work should use smaller changes with tighter verification ## Guardrail Do not let “safe” planning ruin the result on low-risk greenfield work. Do not let “fast” planning justify broad rewrites on live products.

path: CHANGELOG.md
content: # Changelog

## 1.1.0 — 2026-03-30

- Initial ClawHub publish bundle generated from `skills/game-build-strategy/SKILL.md`.
- Added bundle metadata, README, and MANIFEST for OpenClaw / ClawHub distribution.


path: MANIFEST.yaml
content: bundle: game-build-strategy
bundle_version: 1.1.0
bundle_date: 2026-03-30
description: >
  Decide the AI-native development mode, quality target, task granularity, and refactor policy based on project state and user intent. This skill prevents both over-cautious iteration and reckless live-product rewrites.
compatibility:
  designed_for:
    surfaces:
      - chat
      - cli
      - ide
    capabilities:
      - local filesystem access
      - markdown skill bundles
      - reusable game-development workflows
  tested_on:
    - platform: OpenClaw
      surface: ClawHub
      status: pending
      date: 2026-03-30
    - platform: Claude Code
      surface: CLI
      status: pass
      date: 2026-03-30
    - platform: Codex
      surface: CLI
      status: pass
      date: 2026-03-30
  spec_version: agentskills.io/1.0
  frontmatter_mode: metadata
dependencies:
  []
files:
  - path: CHANGELOG.md
    role: reference
    version: 1
    hash: sha256:f60349ef0940c16370ef56569370f7ffb4b18c568b044abffc6b3066253edbe4
    note: Bundle release notes
  - path: README.md
    role: reference
    version: 1
    hash: sha256:f95b39294989e37012b2394c9af120878885443740c9671f901eecafab6a19fa
    note: ClawHub-facing usage and context
  - path: SKILL.md
    role: skill
    version: 1
    hash: sha256:78bafefe481db3fef194e6f28b9dd7e22f36c497e63ecb88a3aa9b38bbd769d5
    note: Canonical skill definition for this publish bundle
  - path: examples/usage.md
    role: reference
    version: 1
    hash: sha256:31519b3d107bf1905543fe0ac0eda50a08c20433982afe00dc9e2b9c0934a080
    note: Referenced support file: examples/usage.md
  - path: shared/reference/development-modes.md
    role: reference
    version: 1
    hash: sha256:b42c75e21c628b0cf55824e1bd8032985bf936ad902d7018ed29897824e32344
    note: Referenced support file: shared/reference/development-modes.md
  - path: shared/reference/quality-targets.md
    role: reference
    version: 1
    hash: sha256:724b5d35ad4182fbdce5145ce9e5d41812155011c923dfb3bcfbff90b06acb0a
    note: Referenced support file: shared/reference/quality-targets.md
  - path: shared/templates/build-strategy.md
    role: reference
    version: 1
    hash: sha256:41497bc63c747e7a07e14f95f6de4df3bf3ec7bbefc9d3dcab8c6967cd3f3094
    note: Referenced support file: shared/templates/build-strategy.md
  - path: shared/templates/quality-target.md
    role: reference
    version: 1
    hash: sha256:85d1340211bfbe36074c8da9b2a2ff2fecd0f2f899c3ef72a121414210e9d005
    note: Referenced support file: shared/templates/quality-target.md
  - path: tests/smoke.md
    role: reference
    version: 1
    hash: sha256:de69e6a62ad775a10d8be9a1db70880b06dbcb8fec70930189ec0267b29ebe1f
    note: Referenced support file: tests/smoke.md


path: README.md
content: # game-build-strategy

Part of the **Game Superpowers** skill system.

## Summary

Decide the AI-native development mode, quality target, task granularity, and refactor policy based on project state and user intent. This skill prevents both over-cautious iteration and reckless live-product rewrites.

## Recommended usage

- Use `game-build-strategy` for this game project and keep the output evidence-based.
- Apply `game-build-strategy` to improve or assess an existing browser game in a focused way.
- Use `game-build-strategy` as part of a larger Game Superpowers workflow when the request clearly matches game build strategy.

## Companion skills

- None

## Source of truth

This publish bundle is derived from the Game Superpowers source repository.
Canonical authoring lives in:

```text
skills/game-build-strategy/SKILL.md
```

## Notes

- This bundle is published for OpenClaw / ClawHub distribution.
- The Game Superpowers repository also supports Claude Code and Codex distributions.
- If a workflow references companion skills, install those companion skills as separate bundles.


path: examples/usage.md
content: # Usage Examples

## Example prompts

- Use `game-build-strategy` for this game project and keep the output evidence-based.
- Apply `game-build-strategy` to improve or assess an existing browser game in a focused way.
- Use `game-build-strategy` as part of a larger Game Superpowers workflow when the request clearly matches game build strategy.

## Expected behavior

- Load the skill instructions from `SKILL.md`.
- Use any packaged `shared/` references when the skill body points to them.
- If the workflow calls for companion skills, tell the user which companion skills should be installed or invoked next.


path: shared/reference/development-modes.md
content: # Development Modes

## yolo-super
Use when:
- the project is greenfield,
- or the user explicitly wants an aggressive rewrite,
- and there are no live-product constraints.

Behavior:
- take large coherent steps,
- allow architecture replacement,
- optimize for best outcome from the same prompt,
- default quality target is usually `polished-prototype`, not `first-playable`.

## guided-build
Use when:
- the project is greenfield or prelaunch,
- but the codebase still needs to remain easy for developers to understand and continue.

Behavior:
- still move quickly,
- but keep boundaries and docs cleaner,
- prefer maintainable architecture from the start.

## refactor-open
Use when:
- the project already exists,
- broad refactors are allowed,
- and the current structure is fighting the requested result.

Behavior:
- preserve what helps,
- replace what blocks quality,
- document migrations and compatibility concerns.

## surgical-live
Use when:
- the project is shipped, live, risky, or highly integrated,
- unless the user explicitly authorizes a broad rewrite.

Behavior:
- minimize blast radius,
- favor compatibility,
- preserve behavior outside the requested change,
- document rollback clearly.


path: shared/reference/quality-targets.md
content: # Quality targets

## first-playable
Use when the point is to validate the fantasy, mechanic, or interaction loop quickly.
Must still be real and bootable, but can defer polish and content breadth.

## polished-prototype
Use when the result needs to impress, demo well, or meaningfully represent the intended game.
This is the default serious greenfield target.

## production-feature
Use when adding or changing a feature inside a maintainable product codebase.
The feature should feel complete, verified, and ready to keep building on.

## live-patch
Use when the repo is shipped or operationally risky.
Prefer small, safe, reversible changes with strong verification and rollback notes.


path: shared/templates/build-strategy.md
content: # Build Strategy Template

## Chosen mode
- **Development mode**:
- **Quality target**:
- **Why**:

## Policy
- **Task sizing policy**:
- **Refactor policy**:
- **Rewrite policy**:
- **Compare-mode policy**:
- **Verification depth**:
- **Rollback expectations**:

## What this means in practice
- **Things we should do aggressively**:
- **Things we should preserve**:
- **Things we should not spend time on**:
- **Things we must not cut even if they are expensive**:


path: shared/templates/quality-target.md
content: # Quality target

- target:
- why:
- must-have bar:
- may defer:
- verification bar:
- stop condition:


path: tests/smoke.md
content: # Smoke Test

Bundle: `game-build-strategy`
Version: `1.1.0`

## Prompt

Use `game-build-strategy` on a fitting game-development task.

## Expected checks

- The agent recognizes the skill's stated purpose.
- The agent uses packaged references when `SKILL.md` points to `./shared/...`.
- The agent does not claim companion skills are bundled implicitly when they are separate installs.
- Companion skills referenced in this bundle: none


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)