[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P4FSXAT0EQZHRWENYFHVR":3,"skill-same:01M71P4FSXAT0EQZHRWENYFHVR":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":46,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M71P4FSXAT0EQZHRWENYFHVR","studio-producer",null,"Use when an org role acts as studio producer and must own scope, schedule and capacity for a creative or game production from pitch to shippable build. Covers trading off scope vs schedule vs capacity, look-ahead risk, just-in-time cuts and milestone tracking. For tooling and vendor ops see studio-operations.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-producer\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"studio","studio producer","producer","for","planning","risk","as","trading","org","game-dev","monomind","leadership","game","milestone","just-in-time","schedule","when","pitch","time","scope","2026-11-10 10:56:23",false,"---\nname: studio-producer\ndescription: \"Use when an org role acts as studio producer and must own scope, schedule and capacity for a creative or game production from pitch to shippable build. Covers trading off scope vs schedule vs capacity, look-ahead risk, just-in-time cuts and milestone tracking. For tooling and vendor ops see studio-operations.\"\ntags: [\"leadership\",\"operations\",\"game-dev\",\"planning\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Studio Producer — Best Practices\n\n## Focus\nOwns scope, schedule, and capacity for a creative\u002Fgame production — the person who keeps a project moving from pitch to shippable build without burning the team out.\n\n## Best practices\n- Track three levers, not one: scope, schedule, and capacity. When one slips, decide explicitly which of the other two absorbs it — never let all three silently degrade.\n- Look 2-3 sprints ahead for risk, not just at the current sprint. Milestones slip because of problems visible weeks earlier that nobody named out loud.\n- Make cut decisions just-in-time, not up front. Lock scope only as late as quality of information allows; protect flexibility for as long as it's cheap.\n- Keep a single visible source of truth for milestones and owners (board, doc) — cross-discipline teams (design\u002Feng\u002Fart\u002Faudio) drift apart without one.\n- Timebox risk-heavy unknowns as spikes with a hard decision date, so ambiguity doesn't quietly eat the whole schedule.\n- Protect crunch as a last resort, not a plan — a schedule that only works if everyone works overtime is not a schedule.\n- Close every milestone with a retro that changes something in the next milestone's plan, not just a status report.\n\n## Common pitfalls\n- Treating the schedule as fixed and scope as the release valve, when scope cuts are usually cheaper and less risky than schedule slips.\n- Reporting \"on track\" from vibes instead of from a burndown against actual remaining scope.\n- Letting a discipline (art, audio, design) work in isolation until integration, discovering conflicts only at milestone review.\n- Overloading the schedule with optional polish before core loop \u002F critical path features are proven.\n\n## Tools & techniques\n- Milestone\u002Fsprint boards (Jira, Trello, ClickUp, Shotgrid) with owner + due date on every card, not just epics.\n- Risk register reviewed weekly: top 3 risks, likelihood, and the specific mitigation in progress.\n- Vertical slice \u002F playable-first milestones to validate the core loop before scaling content.\n- Explicit descope list maintained alongside the roadmap — the pre-agreed cuts if time runs short.\n","# Studio Producer — Best Practices\n\n## Focus\nOwns scope, schedule, and capacity for a creative\u002Fgame production — the person who keeps a project moving from pitch to shippable build without burning the team out.\n\n## Best practices\n- Track three levers, not one: scope, schedule, and capacity. When one slips, decide explicitly which of the other two absorbs it — never let all three silently degrade.\n- Look 2-3 sprints ahead for risk, not just at the current sprint. Milestones slip because of problems visible weeks earlier that nobody named out loud.\n- Make cut decisions just-in-time, not up front. Lock scope only as late as quality of information allows; protect flexibility for as long as it's cheap.\n- Keep a single visible source of truth for milestones and owners (board, doc) — cross-discipline teams (design\u002Feng\u002Fart\u002Faudio) drift apart without one.\n- Timebox risk-heavy unknowns as spikes with a hard decision date, so ambiguity doesn't quietly eat the whole schedule.\n- Protect crunch as a last resort, not a plan — a schedule that only works if everyone works overtime is not a schedule.\n- Close every milestone with a retro that changes something in the next milestone's plan, not just a status report.\n\n## Common pitfalls\n- Treating the schedule as fixed and scope as the release valve, when scope cuts are usually cheaper and less risky than schedule slips.\n- Reporting \"on track\" from vibes instead of from a burndown against actual remaining scope.\n- Letting a discipline (art, audio, design) work in isolation until integration, discovering conflicts only at milestone review.\n- Overloading the schedule with optional polish before core loop \u002F critical path features are proven.\n\n## Tools & techniques\n- Milestone\u002Fsprint boards (Jira, Trello, ClickUp, Shotgrid) with owner + due date on every card, not just epics.\n- Risk register reviewed weekly: top 3 risks, likelihood, and the specific mitigation in progress.\n- Vertical slice \u002F playable-first milestones to validate the core loop before scaling content.\n- Explicit descope list maintained alongside the roadmap — the pre-agreed cuts if time runs short.\n",{"name":5,"tags":43,"tools":45,"source":46,"license":14,"description":7},[29,44,27,22],"operations",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-producer",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add monoes\u002Fmonomind --skill studio-producer",{"tool":61,"command":62},"bunx","bunx skills add monoes\u002Fmonomind --skill studio-producer",{"tool":64,"command":65},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill studio-producer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-producer\u002FSKILL.md",true,[],[70,96,132,159,183,210],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":95},"01M71PB3SHWKMNJM6MD65VX8D6","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[77,78,79,80,81,82,83,84,85,86,87,88,28,89,90,91,92,93,26,94],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":114,"publishedAt":95},"01M71PB18SDG28WBKPKJNB814K","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.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[115,116,117,81,118,119,34,120,86,121,122,123,124,125,126,127,128,129,130,131],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":95},"01M71PAXFM488X9ARXK0T04TF5","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000031","产品经理",[125,143,144,145,146,84,147,34,148,149,150,124,151,152,153,154,155,156,157,158],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":95},"01M71PASSZY800C0RPEARBS918","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000033","数据分析师",[86,125,170,171,21,172,84,157,34,173,174,175,176,150,177,178,179,180,181,182],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":95},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":193,"categoryName":194,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",[196,197,198,199,21,200,201,202,203,85,204,205,206,86,28,177,207,208,209,179],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":95},"01M71PAM19Z1XTV9NPCFSE2MY8","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[216],{"categoryNo":193,"categoryName":194,"taxonomyType":107,"taxonomyTypeDesc":108},[198,218,219,220,221,222,22,21,223,224,121,225,226,29,28,177,227,44,179,228],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","recovery","systems"]