[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NP87K8K00GRAPS3QTH53D":3,"skill-same:01M71NP87K8K00GRAPS3QTH53D":70},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":47,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71NP87K8K00GRAPS3QTH53D","queen-coordinator",null,"Use when an org role acts as queen coordinator and must decompose, delegate and reconcile work within one bounded session whose workers report only to it. Covers authoritative session state, capability routing, acceptance gates, drift correction and not overclaiming consensus. For a multi-level manager\u002Fworker tree, use hierarchical-coord.","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\u002Fqueen-coordinator\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"queen coordinator","coordinator","as","tree","decompose","bounded","capability","org","manager","reconcile","monomind","work","coordination","drift","when","acceptance","only","worker","delegate","consensus","2026-11-10 10:56:23",false,"---\nname: queen-coordinator\ndescription: \"Use when an org role acts as queen coordinator and must decompose, delegate and reconcile work within one bounded session whose workers report only to it. Covers authoritative session state, capability routing, acceptance gates, drift correction and not overclaiming consensus. For a multi-level manager\u002Fworker tree, use hierarchical-coord.\"\ntags: [\"operations\",\"coordination\",\"agents\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Queen Coordinator — Best Practices\n\n## Focus\nSame shape as a lead coordinator — decompose, delegate, hold authoritative state, decide when done — but scoped to a single bounded session with workers that report directly up to it and nowhere else.\n\n## Best practices\n- Own the single source of truth for the session: what's in-progress, blocked, done, and reconciled. Worker reports are inputs to that state, not the state itself.\n- Decompose the session's objective into subtasks with one accountable worker and explicit acceptance criteria each before dispatching anything.\n- Route by capability — match each subtask to the worker actually suited for it rather than whichever worker is idle.\n- Apply the session's approval policy before accepting a deliverable; block anything that fails acceptance criteria with specific, actionable feedback rather than accepting to keep moving.\n- Detect drift early and re-scope immediately — a worker diverging from the session goal costs more the longer it's left uncorrected.\n- Close the session explicitly: reconcile all final worker state into one authoritative record before declaring done, not just when the last worker happens to report in.\n\n## Common pitfalls\n- Treating \"queen\" as implying capabilities the session doesn't actually have — no background timers, no session succession, no automatic redistribution based on inferred worker load. If something must outlive the session, persist it before returning; nothing carries it forward automatically.\n- Rubber-stamping the last worker report instead of reconciling all reports into consistent authoritative state.\n- Letting two workers silently take overlapping scope because delegation wasn't explicit about boundaries.\n- Describing the session as achieving \"consensus\" or being \"fault tolerant\" when it was actually one coordinator making decisions — nothing tolerated a fault, no vote was tallied.\n- Scoping the session too broadly, so \"queen\" coordination is really trying to run a whole hierarchical org through one session instead of one bounded unit of work.\n\n## Tools & techniques\n- Dispatch independent worker tasks in a single batch — that's the only source of real concurrency; the queen doesn't grant parallelism by existing, the dispatch mechanism does.\n- Keep session state (roster, task assignments, acceptance status) in one inspectable place so reconciliation is a read, not a reconstruction.\n- Use an explicit vote\u002Fthreshold mechanism (not the queen's own judgment) for any decision that genuinely needs multiple workers to agree — don't conflate \"queen decides\" with \"workers voted.\"\n- Route synthesis-across-workers to a knowledge-consolidation step distinct from task routing — deciding who does what and reconciling what they collectively learned are different jobs, even in one session.\n","# Queen Coordinator — Best Practices\n\n## Focus\nSame shape as a lead coordinator — decompose, delegate, hold authoritative state, decide when done — but scoped to a single bounded session with workers that report directly up to it and nowhere else.\n\n## Best practices\n- Own the single source of truth for the session: what's in-progress, blocked, done, and reconciled. Worker reports are inputs to that state, not the state itself.\n- Decompose the session's objective into subtasks with one accountable worker and explicit acceptance criteria each before dispatching anything.\n- Route by capability — match each subtask to the worker actually suited for it rather than whichever worker is idle.\n- Apply the session's approval policy before accepting a deliverable; block anything that fails acceptance criteria with specific, actionable feedback rather than accepting to keep moving.\n- Detect drift early and re-scope immediately — a worker diverging from the session goal costs more the longer it's left uncorrected.\n- Close the session explicitly: reconcile all final worker state into one authoritative record before declaring done, not just when the last worker happens to report in.\n\n## Common pitfalls\n- Treating \"queen\" as implying capabilities the session doesn't actually have — no background timers, no session succession, no automatic redistribution based on inferred worker load. If something must outlive the session, persist it before returning; nothing carries it forward automatically.\n- Rubber-stamping the last worker report instead of reconciling all reports into consistent authoritative state.\n- Letting two workers silently take overlapping scope because delegation wasn't explicit about boundaries.\n- Describing the session as achieving \"consensus\" or being \"fault tolerant\" when it was actually one coordinator making decisions — nothing tolerated a fault, no vote was tallied.\n- Scoping the session too broadly, so \"queen\" coordination is really trying to run a whole hierarchical org through one session instead of one bounded unit of work.\n\n## Tools & techniques\n- Dispatch independent worker tasks in a single batch — that's the only source of real concurrency; the queen doesn't grant parallelism by existing, the dispatch mechanism does.\n- Keep session state (roster, task assignments, acceptance status) in one inspectable place so reconciliation is a read, not a reconstruction.\n- Use an explicit vote\u002Fthreshold mechanism (not the queen's own judgment) for any decision that genuinely needs multiple workers to agree — don't conflate \"queen decides\" with \"workers voted.\"\n- Route synthesis-across-workers to a knowledge-consolidation step distinct from task routing — deciding who does what and reconciling what they collectively learned are different jobs, even in one session.\n",{"name":5,"tags":43,"tools":46,"source":47,"license":14,"description":7},[44,30,45],"operations","agents",[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fqueen-coordinator",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add monoes\u002Fmonomind --skill queen-coordinator",{"tool":62,"command":63},"bunx","bunx skills add monoes\u002Fmonomind --skill queen-coordinator",{"tool":65,"command":66},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill queen-coordinator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fqueen-coordinator\u002FSKILL.md",true,[],[71,97,133,158,183,210],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":96},"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",[],[78,79,80,81,82,83,84,85,86,87,88,89,28,90,91,92,93,94,25,95],"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":115,"publishedAt":96},"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",[105,110],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[116,117,118,82,119,120,32,121,87,122,123,124,125,126,127,128,129,130,131,132],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":96},"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",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000031","产品经理",[126,144,145,146,147,85,33,32,148,149,29,125,150,151,152,153,154,155,156,157],"write spec","spec","user request","problem","ask","vague","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":96},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000033","数据分析师",[87,126,169,170,171,172,85,156,32,173,174,175,176,29,177,178,179,180,181,182],"write query","postgres","for","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":96},"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":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":193,"categoryName":194,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000023","Skill与智能体开发",[196,197,198,199,171,200,201,202,203,86,204,205,206,87,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":96},"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":108,"taxonomyTypeDesc":109},[198,218,219,220,221,222,223,171,224,225,122,226,227,228,28,177,229,44,179,230],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","systems"]