From builtin-tasks
Coordination guidelines for leading a team of task-executing agents
npx claudepluginhub motlin/claude-code-plugins --plugin builtin-tasksThis skill uses the workspace's default tool permissions.
Every task must result in exactly one commit. Before assigning the next task to a member, verify their previous work was committed.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Every task must result in exactly one commit. Before assigning the next task to a member, verify their previous work was committed.
Before assigning tasks in parallel, read each task's description to identify which files it modifies. If two tasks touch the same files, do NOT assign them simultaneously — either serialize them or instruct one member to use a worktree.
Use judgement on whether parallelism even makes sense. If most tasks touch overlapping files, it may be simpler to run them sequentially. If using worktrees, instruct the member to git worktree add into a peer directory before starting.
Whenever no team members are actively running, verify that all changes have been committed. There should be no uncommitted changes at rest.