Game Studio Delivery And Commercial Operations logo

Game Studio Delivery And Commercial Operations

Community
peterbamuhigire
game-studio-delivery-and-commercial-operations

Use when running game discovery, estimation, staffing, RACI, greenlight, statements of work, milestone governance, outsourcing, client demos, change control, launch command, postmortems, or evidence-based case studies.

Overview

Publisherpeterbamuhigire
Repositorychwezi-dev-engine
Skill namegame-studio-delivery-and-commercial-operations
Stars
29
Forks
6
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by peterbamuhigire on GitHub. Read the source before you install it.

Installation

Install the Game Studio Delivery And Commercial Operations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/peterbamuhigire/chwezi-dev-engine/tree/main/skills/game-development/game-studio-delivery-and-commercial-operations
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/peterbamuhigire/chwezi-dev-engine.git /tmp/chwezi-dev-engine
mkdir -p .claude/skills
cp -r /tmp/chwezi-dev-engine/skills/game-development/game-studio-delivery-and-commercial-operations .claude/skills/game-studio-delivery-and-commercial-operations
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Game Studio Delivery And Commercial Operations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Game Studio Delivery And Commercial Operations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Game Studio Delivery And Commercial Operations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Game Studio Delivery and Commercial Operations

Make scope, uncertainty, content throughput, accountability, acceptance, and commercial change visible from discovery through support.

Use When

  • Planning or governing a client game engagement, studio milestone, outsourcing package, greenlight, launch, or case study.

Do Not Use When

  • Creative, technical, legal, or financial specialists have not approved their own assumptions.

Required Inputs

Client/owner decision, product/platform/audience scope, evidence, team/vendor capabilities, dependencies, rights, risks, milestone model, content inventory, throughput history, business-model hypotheses, budget/runway/contract constraints, acceptance, change process, support obligations, and stop conditions.

Workflow

  1. Run discovery and technical due diligence; separate facts, assumptions, exclusions, and client-owned inputs.
  2. Estimate systems and content with range/confidence, throughput basis, rework, integration, certification, contingency, and recalibration triggers.
  3. Define milestone RACI, RAID, decision rights, artefacts, objective acceptance, demo script, and payment/change links.
  4. Gate vendors with provenance, source-file, technical, security, and integration acceptance.
  5. Conduct greenlight and milestone reviews from evidence; rehearse launch command, support, rollback, and postmortem.
  6. Publish case evidence only for demonstrable outcomes, with client permission and limitations.

Compare premium, demo/prologue, DLC, subscription, sponsorship, licensing, institutional sales, grants, ethical ads and IAP as hypotheses. Expose price/cost/tax/store/payment/rights/localisation/support/content-throughput assumptions as ranges with sources and recalibration triggers. Treat financial independence as motivation for disciplined portfolio economics and reusable IP, never as a promised outcome.

For an ad-supported case, require the non-intrusive-ad contract, vendor/data/legal review, no-ads or kill-switch path, placement/cap/pace evidence, creative controls, real-device failure tests and player trust/wellbeing guardrails. Do not greenlight from eCPM or fill-rate claims alone.

Quality Standards

  • Estimates show basis, range, confidence, dependencies, rework, lifecycle cost and recalibration triggers.
  • Milestones are outcome- and evidence-based, with accountable acceptance, residual risk and change control.
  • Commercial models preserve assumptions, downside, rights, tax/payment/platform review and explicit greenlight, pivot, narrow, hold or stop criteria.
  • Vendor and advertising acceptance includes technical, privacy, child-safety, accessibility, creative-quality, support, data-exit and rollback evidence.

Outputs

Discovery pack; estimate basis/range; staffing/RACI; SOW acceptance schedule; RAID/change/decision logs; vendor briefs; greenlight and milestone records; launch/postmortem; case-evidence register.

Decision Rules

Evidence stateDecision
Demand, price or conversion rests on analogy aloneRun a bounded market/product test; keep forecast unapproved
Runway cannot fund the next evidence gate plus contingencyNarrow, hold or stop
Business model harms fairness, children, culture or trustReject or redesign regardless of projected revenue
Reuse would erase a game's identity or performance simplicityKeep capability shared but content/system expression project-specific

Anti-Patterns

  • FIRE target turned into a revenue promise. Fix: show assumptions, downside and stop rules.
  • Percentage-complete greenlight. Fix: require outcome evidence and residual risk.
  • Cheap content estimate without rework/localisation/support. Fix: include complete lifecycle cost.
  • Ad vendor selected on headline yield. Fix: gate privacy, child safety, integration, creative quality, exit and trust.
  • Shared platform forced into every game. Fix: consume reusable capabilities selectively.

References

Evidence Produced

CategoryArtifactFormatExample
OperabilityGame delivery and greenlight evidence packMarkdown/workbookscope, estimate, staffing, milestone, dependency, commercial risk, decision, and owner

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Game Studio Delivery And Commercial Operations AI skill do?

Use when running game discovery, estimation, staffing, RACI, greenlight, statements of work, milestone governance, outsourcing, client demos, change control, launch command, postmortems, or evidence-based case studies.

Why use Game Studio Delivery And Commercial Operations on TypingMind?

Because you install it once and use it with any model. Game Studio Delivery And Commercial Operations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Game Studio Delivery And Commercial Operations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/peterbamuhigire/chwezi-dev-engine/tree/main/skills/game-development/game-studio-delivery-and-commercial-operations. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Game Studio Delivery And Commercial Operations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Game Studio Delivery And Commercial Operations?

As many as you like. As long as a model supports skills, you can use Game Studio Delivery And Commercial Operations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Game Studio Delivery And Commercial Operations AI skill free?

Yes. It is published on GitHub by peterbamuhigire under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇