[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GFS4HWZEAM1JWHY2EPCRA":3,"skill-same:01M75GFS4HWZEAM1JWHY2EPCRA":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75GFS4HWZEAM1JWHY2EPCRA","task-coordination-strategies",null,"Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-coordination-strategies\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: task-coordination-strategies\ndescription: Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.\nversion: 1.0.2\n---\n\n# Task Coordination Strategies\n\nStrategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams.\n\n## When to Use This Skill\n\n- Breaking down a complex task for parallel execution\n- Designing task dependency relationships (blockedBy\u002Fblocks)\n- Writing task descriptions with clear acceptance criteria\n- Monitoring and rebalancing workload across teammates\n- Identifying the critical path in a multi-task workflow\n\n## Task Decomposition Strategies\n\n### By Layer\n\nSplit work by architectural layer:\n\n- Frontend components\n- Backend API endpoints\n- Database migrations\u002Fmodels\n- Test suites\n\n**Best for**: Full-stack features, vertical slices\n\n### By Component\n\nSplit work by functional component:\n\n- Authentication module\n- User profile module\n- Notification module\n\n**Best for**: Microservices, modular architectures\n\n### By Concern\n\nSplit work by cross-cutting concern:\n\n- Security review\n- Performance review\n- Architecture review\n\n**Best for**: Code reviews, audits\n\n### By File Ownership\n\nSplit work by file\u002Fdirectory boundaries:\n\n- `src\u002Fcomponents\u002F` — Implementer 1\n- `src\u002Fapi\u002F` — Implementer 2\n- `src\u002Futils\u002F` — Implementer 3\n\n**Best for**: Parallel implementation, conflict avoidance\n\n## Dependency Graph Design\n\n### Principles\n\n1. **Minimize chain depth** — Prefer wide, shallow graphs over deep chains\n2. **Identify the critical path** — The longest chain determines minimum completion time\n3. **Use blockedBy sparingly** — Only add dependencies that are truly required\n4. **Avoid circular dependencies** — Task A blocks B blocks A is a deadlock\n\n### Patterns\n\n**Independent (Best parallelism)**:\n\n```\nTask A ─┐\nTask B ─┼─→ Integration\nTask C ─┘\n```\n\n**Sequential (Necessary dependencies)**:\n\n```\nTask A → Task B → Task C\n```\n\n**Diamond (Mixed)**:\n\n```\n        ┌→ Task B ─┐\nTask A ─┤          ├→ Task D\n        └→ Task C ─┘\n```\n\n### Using blockedBy\u002Fblocks\n\n```\nTaskCreate: { subject: \"Build API endpoints\" }         → Task #1\nTaskCreate: { subject: \"Build frontend components\" }    → Task #2\nTaskCreate: { subject: \"Integration testing\" }          → Task #3\nTaskUpdate: { taskId: \"3\", addBlockedBy: [\"1\", \"2\"] }  → #3 waits for #1 and #2\n```\n\n## Task Description Best Practices\n\nEvery task should include:\n\n1. **Objective** — What needs to be accomplished (1-2 sentences)\n2. **Owned Files** — Explicit list of files\u002Fdirectories this teammate may modify\n3. **Requirements** — Specific deliverables or behaviors expected\n4. **Interface Contracts** — How this work connects to other teammates' work\n5. **Acceptance Criteria** — How to verify the task is done correctly\n6. **Scope Boundaries** — What is explicitly out of scope\n\n### Template\n\n```\n## Objective\nBuild the user authentication API endpoints.\n\n## Owned Files\n- src\u002Fapi\u002Fauth.ts\n- src\u002Fapi\u002Fmiddleware\u002Fauth-middleware.ts\n- src\u002Ftypes\u002Fauth.ts (shared — read only, do not modify)\n\n## Requirements\n- POST \u002Fapi\u002Flogin — accepts email\u002Fpassword, returns JWT\n- POST \u002Fapi\u002Fregister — creates new user, returns JWT\n- GET \u002Fapi\u002Fme — returns current user profile (requires auth)\n\n## Interface Contract\n- Import User type from src\u002Ftypes\u002Fauth.ts (owned by implementer-1)\n- Export AuthResponse type for frontend consumption\n\n## Acceptance Criteria\n- All endpoints return proper HTTP status codes\n- JWT tokens expire after 24 hours\n- Passwords are hashed with bcrypt\n\n## Out of Scope\n- OAuth\u002Fsocial login\n- Password reset flow\n- Rate limiting\n```\n\n## Workload Monitoring\n\n### Indicators of Imbalance\n\n| Signal                     | Meaning             | Action                      |\n| -------------------------- | ------------------- | --------------------------- |\n| Teammate idle, others busy | Uneven distribution | Reassign pending tasks      |\n| Teammate stuck on one task | Possible blocker    | Check in, offer help        |\n| All tasks blocked          | Dependency issue    | Resolve critical path first |\n| One teammate has 3x others | Overloaded          | Split tasks or reassign     |\n\n### Rebalancing Steps\n\n1. Call `TaskList` to assess current state\n2. Identify idle or overloaded teammates\n3. Use `TaskUpdate` to reassign tasks\n4. Use `SendMessage` to notify affected teammates\n5. Monitor for improved throughput\n","# Task Coordination Strategies\n\nStrategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams.\n\n## When to Use This Skill\n\n- Breaking down a complex task for parallel execution\n- Designing task dependency relationships (blockedBy\u002Fblocks)\n- Writing task descriptions with clear acceptance criteria\n- Monitoring and rebalancing workload across teammates\n- Identifying the critical path in a multi-task workflow\n\n## Task Decomposition Strategies\n\n### By Layer\n\nSplit work by architectural layer:\n\n- Frontend components\n- Backend API endpoints\n- Database migrations\u002Fmodels\n- Test suites\n\n**Best for**: Full-stack features, vertical slices\n\n### By Component\n\nSplit work by functional component:\n\n- Authentication module\n- User profile module\n- Notification module\n\n**Best for**: Microservices, modular architectures\n\n### By Concern\n\nSplit work by cross-cutting concern:\n\n- Security review\n- Performance review\n- Architecture review\n\n**Best for**: Code reviews, audits\n\n### By File Ownership\n\nSplit work by file\u002Fdirectory boundaries:\n\n- `src\u002Fcomponents\u002F` — Implementer 1\n- `src\u002Fapi\u002F` — Implementer 2\n- `src\u002Futils\u002F` — Implementer 3\n\n**Best for**: Parallel implementation, conflict avoidance\n\n## Dependency Graph Design\n\n### Principles\n\n1. **Minimize chain depth** — Prefer wide, shallow graphs over deep chains\n2. **Identify the critical path** — The longest chain determines minimum completion time\n3. **Use blockedBy sparingly** — Only add dependencies that are truly required\n4. **Avoid circular dependencies** — Task A blocks B blocks A is a deadlock\n\n### Patterns\n\n**Independent (Best parallelism)**:\n\n```\nTask A ─┐\nTask B ─┼─→ Integration\nTask C ─┘\n```\n\n**Sequential (Necessary dependencies)**:\n\n```\nTask A → Task B → Task C\n```\n\n**Diamond (Mixed)**:\n\n```\n        ┌→ Task B ─┐\nTask A ─┤          ├→ Task D\n        └→ Task C ─┘\n```\n\n### Using blockedBy\u002Fblocks\n\n```\nTaskCreate: { subject: \"Build API endpoints\" }         → Task #1\nTaskCreate: { subject: \"Build frontend components\" }    → Task #2\nTaskCreate: { subject: \"Integration testing\" }          → Task #3\nTaskUpdate: { taskId: \"3\", addBlockedBy: [\"1\", \"2\"] }  → #3 waits for #1 and #2\n```\n\n## Task Description Best Practices\n\nEvery task should include:\n\n1. **Objective** — What needs to be accomplished (1-2 sentences)\n2. **Owned Files** — Explicit list of files\u002Fdirectories this teammate may modify\n3. **Requirements** — Specific deliverables or behaviors expected\n4. **Interface Contracts** — How this work connects to other teammates' work\n5. **Acceptance Criteria** — How to verify the task is done correctly\n6. **Scope Boundaries** — What is explicitly out of scope\n\n### Template\n\n```\n## Objective\nBuild the user authentication API endpoints.\n\n## Owned Files\n- src\u002Fapi\u002Fauth.ts\n- src\u002Fapi\u002Fmiddleware\u002Fauth-middleware.ts\n- src\u002Ftypes\u002Fauth.ts (shared — read only, do not modify)\n\n## Requirements\n- POST \u002Fapi\u002Flogin — accepts email\u002Fpassword, returns JWT\n- POST \u002Fapi\u002Fregister — creates new user, returns JWT\n- GET \u002Fapi\u002Fme — returns current user profile (requires auth)\n\n## Interface Contract\n- Import User type from src\u002Ftypes\u002Fauth.ts (owned by implementer-1)\n- Export AuthResponse type for frontend consumption\n\n## Acceptance Criteria\n- All endpoints return proper HTTP status codes\n- JWT tokens expire after 24 hours\n- Passwords are hashed with bcrypt\n\n## Out of Scope\n- OAuth\u002Fsocial login\n- Password reset flow\n- Rate limiting\n```\n\n## Workload Monitoring\n\n### Indicators of Imbalance\n\n| Signal                     | Meaning             | Action                      |\n| -------------------------- | ------------------- | --------------------------- |\n| Teammate idle, others busy | Uneven distribution | Reassign pending tasks      |\n| Teammate stuck on one task | Possible blocker    | Check in, offer help        |\n| All tasks blocked          | Dependency issue    | Resolve critical path first |\n| One teammate has 3x others | Overloaded          | Split tasks or reassign     |\n\n### Rebalancing Steps\n\n1. Call `TaskList` to assess current state\n2. Identify idle or overloaded teammates\n3. Use `TaskUpdate` to reassign tasks\n4. Use `SendMessage` to notify affected teammates\n5. Monitor for improved throughput\n",{"name":5,"version":23,"description":7},"1.0.2","main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Ftask-coordination-strategies",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add RudyCity\u002Fsuperagent --skill task-coordination-strategies",{"tool":37,"command":38},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill task-coordination-strategies",{"tool":40,"command":41},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill task-coordination-strategies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-coordination-strategies\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fdependency-graphs.md","REFERENCE","参考文档",2706,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-coordination-strategies\u002Freferences\u002Fdependency-graphs.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ftask-decomposition.md",2738,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-coordination-strategies\u002Freferences\u002Ftask-decomposition.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]