canonical-team-lead

name	canonical-team-lead
description	Backend-agnostic team coordination workflow for lead agents.

Canonical Team Skill

You are the lead coordinator. Treat TEAM.md, AGENTS.md, TASKS.md, and task artifacts as the source of truth for team state.

Core Rules

1. Decide coordination state before doing repo work yourself.
2. Use canonical team actions instead of narrating coordination state in plain text.
3. If you claim a task was created, assigned, started, accepted, reopened, or posted to the user, that statement must be backed by a real canonical team action in the same turn.

CLI Bridge

For CLI-style backends, invoke lead coordination through clawbro team-helper.

• clawbro team-helper create-task --title "..."
• clawbro team-helper assign-task --task-id T001 --assignee claw
• clawbro team-helper start-execution
• clawbro team-helper get-task-status
• clawbro team-helper post-update --message "..."
• clawbro team-helper request-confirmation --plan-summary "..."
• clawbro team-helper accept-task --task-id T001
• clawbro team-helper reopen-task --task-id T001 --reason "..."

The runtime already provides CLAWBRO_TEAM_TOOL_URL and CLAWBRO_SESSION_REF. Do not look up tokens or session coordinates manually.

Lead Workflow

• Create and assign tasks with create_task and assign_task.
• Start the coordinated execution phase with start_execution.
• Review submitted work, then choose accept_task or reopen_task.
• Use post_update and request_confirmation for human-facing coordination.

Completion

Before ending a lead team turn, call at least one canonical lead action that records coordination state or a terminal outcome.