AGENT SKILL

studio-operations

Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer.

License 许可
Apache-2.0
所属仓库
monoes/monomind
最近更新
2026-11-14
Stars
★ 23
Forks
2

01 前言 Front Matter

name
studio-operations
tags
[ "leadership", "operations", "game-dev" ]
tools
[]
source
https://github.com/monoes/monomind
license
Apache-2.0
description
Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer.

03 SKILL.md 正文

Studio Operations — Best Practices

Focus

Keeps the studio's operating infrastructure running — tools, pipelines, budgets, vendor/contractor logistics, and the processes that let creative teams focus on making the thing instead of fighting the environment.

Best practices

  • Treat tooling and pipeline friction as a first-class backlog item, not an afterthought — time lost to broken build pipelines or asset tools compounds across the whole team.
  • Keep budget burn visible and tied to milestones, not just calendar months — a team can be "on budget" monthly while badly overspent against remaining scope.
  • Standardize repeatable processes (onboarding, asset submission, build cadence) so they don't depend on one person's memory.
  • Negotiate vendor/contractor terms with clear deliverables and kill criteria before work starts, not after it's late.
  • Audit access and licenses periodically — unused seats and stale permissions are both cost and risk.
  • Build in slack for the unglamorous work (tooling upkeep, license renewals, backup verification) — it never wins a prioritization fight on its own.
  • Make the studio's operating rhythm (standups, reviews, builds) predictable enough that people can plan around it.

Common pitfalls

  • Letting pipeline/tooling debt accumulate because it's invisible until it causes a production-blocking failure.
  • Tracking budget against total allocation instead of against burn rate relative to remaining milestones.
  • Onboarding new contractors/hires ad hoc each time instead of maintaining a repeatable checklist.
  • Treating operations as purely reactive (firefighting) instead of building preventive process.

Tools & techniques

  • Burn-rate dashboards tied to milestone completion, not just calendar spend.
  • Standardized onboarding/offboarding checklists for contractors, vendors, and new hires.
  • Pipeline health checks (build times, asset submission failures) tracked over time like any other metric.
  • Vendor scorecards — deliverable quality, timeliness, cost — reviewed before renewal decisions.

04 同仓库更多 Skills

monoes
monoes/monomind

zk-steward

Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.

★ 23
monoes
monoes/monomind

writing-plans

Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.

内容创作者写作与文案
★ 23
monoes
monoes/monomind

write-spec

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

产品经理
★ 23
monoes
monoes/monomind

write-query

Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.

数据分析师
★ 23
monoes
monoes/monomind

workflow-automation

Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.

运维与部署Skill与智能体开发
★ 23
monoes
monoes/monomind

workflow-architect

Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.

Skill与智能体开发
★ 23