Game Jam Planning & Submission

À propos de ce Skill

Scope a jam entry to its deadline, schedule work, cut features, verify a clean build, and submit on time.

Pourquoi ce choix

Provides a focused workflow, implementation patterns, and common failure checks for game jam planning & submission. Pair it with the detected engine and any related systems required by the task.

À quoi il sert

• Use when your game task needs game jam planning & submission.

What this skill helps you build

Scope a jam entry to its deadline, schedule work, cut features, verify a clean build, and submit on time.

Original game-jam instructions

Patterns in the upstream playbook

The entrypoint covers: Scope budget by jam length (plan backwards from the deadline); The 48-hour timeline (concrete blocks); Feature triage — decide fast, decide out loud; Pre-submission build check (run on a clean copy, not your dev folder).

Original game-jam instructions

Use it in your project

1. Inspect the existing project

   Describe the desired behavior and share the relevant project files, engine version, and current failure or target result.

2. Apply the focused playbook

   Scope a jam entry to its deadline, schedule work, cut features, verify a clean build, and submit on time.

3. Verify in the matching runtime

   Run the project or workflow with its actual dependencies and check the changed behavior before accepting the result.

Original game-jam instructionsEngine versions and upgrade policy

Shared collection installation

Install the complete upstream collection with its router and keep each skill’s bundled references, scripts, and assets. The dispatcher selects an engine and the smallest relevant task set; a member listing is a focused entry into that shared package.

Upstream installation guide

Avant de l’utiliser

• A game project and the tools or account required for the selected workflow. Review the actual target build before submission or publication.

Agents compatibles