菜单
Task Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/yonatangross/orchestkit --skill task-dependency-patterns命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Chain patterns for multi-phase pipelines: MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building or debugging a pipeline skill.
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned entries, and checks CC version matrix compliance. Use when diagnosing plugin health, troubleshooting configuration issues, or running pre-release checks.
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are drift-vulnerable. Read-only — never modifies telemetry files.
正在显示 SKILL.md
| name | task-dependency-patterns |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | Task Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status. |
| context | fork |
| version | 1.0.0 |
| author | OrchestKit |
| agent | workflow-architect |
| tags | ["task-management","dependencies","orchestration","workflow","coordination"] |
| user-invocable | false |
| disable-model-invocation | true |
| complexity | medium |
| persuasion-type | reference |
| metadata | {"category":"workflow-automation"} |
| allowed-tools | ["Read","Glob","Grep","WebFetch","WebSearch"] |
| tool-coverage | illustrative |
Claude Code 2.1.16 introduces a native Task Management System with four tools:
Tasks enable structured work tracking, parallel coordination, and clear progress visibility.
Break complex work into atomic, trackable units:
Feature: Add user authentication
Tasks:
#1. [pending] Create User model
#2. [pending] Add auth endpoints (blockedBy: #1)
#3. [pending] Implement JWT tokens (blockedBy: #2)
#4. [pending] Add auth middleware (blockedBy: #3)
#5. [pending] Write integration tests (blockedBy: #4)
Use addBlockedBy to create execution order:
// Task #3 cannot start until #1 and #2 complete
{"taskId": "3", "addBlockedBy": ["1", "2"]}
pending → in_progress → completed
↓ ↓
(unblocked) (active)
pending/in_progress → deleted
Use status: "deleted" to permanently remove tasks:
// Delete a task
{"taskId": "3", "status": "deleted"}
When to delete:
When NOT to delete:
Provide present-continuous form for spinner display:
| subject (imperative) | activeForm (continuous) |
|---|---|
| Run tests | Running tests |
| Update schema | Updating schema |
| Fix authentication | Fixing authentication |
Agent Teams provides multi-agent coordination with shared task lists and peer-to-peer messaging.
CC 2.1.161 — independent parallel-tool failure: A failed tool call in a parallel batch no longer cancels siblings; each returns its own result. Teammates must check task status independently and handle failures explicitly rather than assuming a batch-wide abort.
1. (implicit team — CC 2.1.178+) → one team per session; no TeamCreate
2. TaskCreate(subject, description) → Add tasks to shared list
3. Agent(name, team_name, prompt) → Spawn teammates into the implicit team
4. TaskUpdate(owner: "teammate-name") → Assign tasks
5. SendMessage(to, message, summary) → Direct teammate communication
6. (turn / background ends) → teammates wind down; Ctrl+F x2 for bg
| Criteria | Task Tool (subagents) | Agent Teams |
|---|---|---|
| Independent tasks | Yes | Overkill |
| Cross-cutting changes | Limited | Yes |
| Agents need to talk | No (star topology) | Yes (mesh) |
| Cost sensitivity | Lower (~1x) | Higher (~2.5x) |
| Complexity < 3.0 | Yes | No |
| Complexity > 3.5 | Possible | Recommended |
# Spawn teammate into shared task list
Agent(
prompt="You are the backend architect...",
team_name="my-feature",
name="backend-architect",
subagent_type="ork:backend-system-architect"
)
# Teammate claims and works tasks
TaskList → find unblocked, unowned tasks
TaskUpdate(taskId, owner: "backend-architect", status: "in_progress")
# ... do work ...
TaskUpdate(taskId, status: "completed")
TaskList → find next task
# Direct message between teammates (params: to, message, summary)
SendMessage(to: "frontend-dev",
message: "API contract ready: GET /users/:id returns {...}",
summary: "API contract shared")
# No broadcast primitive — send to each teammate, or post to the shared
# task list (TaskCreate/TaskUpdate) so every teammate sees it
SendMessage(to: "backend-dev",
message: "Breaking change: auth header format changed",
summary: "Breaking auth change")
When using Agent Teams, if context limit is reached mid-workflow:
TaskListTaskUpdate(taskId: task_id, status: "completed", metadata: {"skipped": "context limit"})ork:implement - Implementation workflow with task tracking and progress updatesork:verify - Verification tasks and completion checklistsork:fix-issue - Issue resolution with hypothesis-based RCA trackingork:brainstorm - Design exploration with parallel agent tasksLoad on demand with Read("${CLAUDE_PLUGIN_ROOT}/skills/task-dependency-patterns/references/<file>"):
| File | Content |
|---|---|
dependency-tracking.md | Dependency tracking patterns |
status-workflow.md | Status workflow details |
multi-agent-coordination.md | Multi-agent coordination |