[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETDQVBKGVCBTBZDEDNEZDP":3,"skill-same:01M7ETDQVBKGVCBTBZDEDNEZDP":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ETDQVBKGVCBTBZDEDNEZDP","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftask-coordination-strategies\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"description":7},"1.0.2","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Ftask-coordination-strategies",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill task-coordination-strategies",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill task-coordination-strategies",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill task-coordination-strategies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftask-coordination-strategies\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdependency-graphs.md","REFERENCE","参考文档",2706,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftask-coordination-strategies\u002Freferences\u002Fdependency-graphs.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ftask-decomposition.md",2738,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Ftask-coordination-strategies\u002Freferences\u002Ftask-decomposition.md",[58,66,71,78,85,92],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":67,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":65},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":65},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":65},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":65},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":65},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]