stevehuang0115/crewly/assign-ticket

Assign Ticket (Team Leader)

Project tickets are the project's own backlog (see the project-tickets skill). Workers take ready tickets themselves when they are idle; use this when you want a specific worker on a specific ticket.

# Start work now: the ticket goes in_progress and the worker gets a WorkItem
bash {{TL_SKILLS_PATH}}/assign-ticket/execute.sh --project /path/to/project --id APP-12 --to worker-session
 
# Only record who will do it (no WorkItem yet)
bash {{TL_SKILLS_PATH}}/assign-ticket/execute.sh --project /path/to/project --id APP-12 --to worker-session --no-start

Rules the backend enforces:

• You must lead a team that works on the project.
• The worker must be on a team of that project (and on the ticket's team, if

it names one).

• A ticket that is already in progress must be released first

(project-tickets release), so two workers never hold one ticket.

When the worker completes the WorkItem, you review it through the normal verification item; once you verify it the ticket moves to done by itself.

Paused teams

The owner can pause a team temporarily (specs/2026-10-04-team-pause.md). A paused team is hidden from agents and takes no work: handing it work, or messaging, starting or assigning a ticket to one of its members, fails with code: "team_paused" and a message saying what to do instead — usually gh issue create -R <repo> --title "…" --body "…" (the team's issue repo), otherwise tell the orc. Do that; do not retry or route around the pause.