[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P5G4ANQMKCD3JQES7A6P2":3,"skill-same:01M71P5G4ANQMKCD3JQES7A6P2":73},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":50,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71P5G4ANQMKCD3JQES7A6P2","task-orchestrator",null,"Use when an org role acts as task orchestrator and must run multi-agent work: sequence phases, hand off context, enforce gates, retry or escalate. Covers small verifiable tasks, explicit state tracking and capped retries.","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\u002Ftask-orchestrator\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"task","orchestrator","task orchestrator","github","monomind","work","state","multi","gates","hand","coordination","tasks","query","when","use","impact","retries","enforce","retry","as","2026-11-10 10:56:31",false,"---\nname: task-orchestrator\ndescription: \"Use when an org role acts as task orchestrator and must run multi-agent work: sequence phases, hand off context, enforce gates, retry or escalate. Covers small verifiable tasks, explicit state tracking and capped retries.\"\ntags: [\"engineering\",\"coordination\",\"agents\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_impact\"]\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Task Orchestrator — Best Practices\n\n## Focus\nCoordinates multi-step, multi-agent work end-to-end — sequencing phases, handing off context between specialists, enforcing quality gates, and deciding when to retry, escalate, or advance.\n\n## Best practices\n- Break work into the smallest independently-verifiable tasks, and require each to pass its own check before advancing — no batch-and-hope.\n- Give every handoff full context: what was done, what's expected next, and any prior feedback — agents fail when they receive vague instructions.\n- Track explicit state (current phase, task, retry count, blockers) so progress is inspectable at any point, not just inferred from logs.\n- Cap retries per task (e.g. 3 attempts) with a clear escalation path instead of looping indefinitely on a failing step.\n- Never advance a phase until its quality gate is met — skipping validation to \"keep moving\" compounds failures downstream.\n- Route each task to the specialist best suited for it rather than a generalist, and be explicit about why.\n- Prefer parallelizing independent tasks and serializing only genuine dependencies — false serialization wastes the most time in orchestration.\n- Report status with data (task N\u002FM complete, retry count, blockers) rather than vague progress claims.\n\n## Common pitfalls\n- Advancing to the next phase because an agent claimed success, without independent verification of the actual output.\n- Serializing tasks that have no real dependency between them, when they could run concurrently.\n- Losing context on handoff — the next agent re-derives requirements from scratch instead of inheriting them.\n- Retrying a failing task with identical instructions instead of incorporating the specific failure feedback into the retry.\n- Treating \"agent didn't error\" as equivalent to \"task is done correctly\" — completion and correctness are different checks.\n\n## Tools & techniques\n- Explicit state machines\u002Fplans (phase → task → retry-count → status) rather than ad hoc coordination via chat history.\n- Dependency graphs to identify which tasks can run in parallel vs. must be sequential.\n- Quality gates with concrete pass\u002Ffail criteria (tests pass, QA sign-off, schema validation) attached to each phase transition.\n- Structured status\u002Fcompletion reports (tasks total\u002Fcompleted\u002Fblocked, retries used, next action) for both human and downstream-agent consumption.\n- Circuit-breaker style escalation: after N failed retries, stop looping and surface the blocker instead of silently continuing.\n","# Task Orchestrator — Best Practices\n\n## Focus\nCoordinates multi-step, multi-agent work end-to-end — sequencing phases, handing off context between specialists, enforcing quality gates, and deciding when to retry, escalate, or advance.\n\n## Best practices\n- Break work into the smallest independently-verifiable tasks, and require each to pass its own check before advancing — no batch-and-hope.\n- Give every handoff full context: what was done, what's expected next, and any prior feedback — agents fail when they receive vague instructions.\n- Track explicit state (current phase, task, retry count, blockers) so progress is inspectable at any point, not just inferred from logs.\n- Cap retries per task (e.g. 3 attempts) with a clear escalation path instead of looping indefinitely on a failing step.\n- Never advance a phase until its quality gate is met — skipping validation to \"keep moving\" compounds failures downstream.\n- Route each task to the specialist best suited for it rather than a generalist, and be explicit about why.\n- Prefer parallelizing independent tasks and serializing only genuine dependencies — false serialization wastes the most time in orchestration.\n- Report status with data (task N\u002FM complete, retry count, blockers) rather than vague progress claims.\n\n## Common pitfalls\n- Advancing to the next phase because an agent claimed success, without independent verification of the actual output.\n- Serializing tasks that have no real dependency between them, when they could run concurrently.\n- Losing context on handoff — the next agent re-derives requirements from scratch instead of inheriting them.\n- Retrying a failing task with identical instructions instead of incorporating the specific failure feedback into the retry.\n- Treating \"agent didn't error\" as equivalent to \"task is done correctly\" — completion and correctness are different checks.\n\n## Tools & techniques\n- Explicit state machines\u002Fplans (phase → task → retry-count → status) rather than ad hoc coordination via chat history.\n- Dependency graphs to identify which tasks can run in parallel vs. must be sequential.\n- Quality gates with concrete pass\u002Ffail criteria (tests pass, QA sign-off, schema validation) attached to each phase transition.\n- Structured status\u002Fcompletion reports (tasks total\u002Fcompleted\u002Fblocked, retries used, next action) for both human and downstream-agent consumption.\n- Circuit-breaker style escalation: after N failed retries, stop looping and surface the blocker instead of silently continuing.\n",{"name":5,"tags":43,"tools":46,"source":50,"license":14,"description":7},[44,28,45],"engineering","agents",[47,48,49],"monograph_query","monograph_context","monograph_impact","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ftask-orchestrator",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add monoes\u002Fmonomind --skill task-orchestrator",{"tool":65,"command":66},"bunx","bunx skills add monoes\u002Fmonomind --skill task-orchestrator",{"tool":68,"command":69},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill task-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ftask-orchestrator\u002FSKILL.md",true,[],[74,99,134,159,182,209],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":98},"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",[],[81,82,83,84,85,86,87,88,33,30,89,90,22,91,92,93,94,95,96,97],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":117,"publishedAt":98},"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",[107,112],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[118,119,120,85,121,122,31,123,30,124,29,125,126,127,128,129,130,131,132,133],"writing","writing plans","plans","superpowers","implementation plan","you","code","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":98},"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",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000031","产品经理",[127,145,146,147,148,88,149,31,150,151,23,126,152,153,154,155,156,157,32,158],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","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":98},"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":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000033","数据分析师",[30,127,170,171,172,173,88,32,31,174,175,176,25,23,21,177,178,179,180,181],"write query","postgres","for","snowflake","best practices","natural-language","with","sql","https","syntax","plugins","data",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":194,"publishedAt":98},"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",[188,191],{"categoryNo":189,"categoryName":190,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":192,"categoryName":193,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000023","Skill与智能体开发",[195,196,197,198,172,199,200,201,202,33,203,204,205,30,22,21,206,207,208,178],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":98},"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",[215],{"categoryNo":192,"categoryName":193,"taxonomyType":110,"taxonomyTypeDesc":111},[197,217,218,219,220,221,222,172,223,224,124,225,24,226,22,21,227,228,178,229],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","leadership","recovery","operations","systems"]