# Team Lead

Run a goal as a team when you can also do the work yourself: decide what you keep...

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill team-lead -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill team-lead -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill team-lead -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill team-lead -g -a gemini-cli -y`

## Description

Run a goal as a team when you can also do the work yourself: decide what you keep, dispatch the rest, and keep the status board honest. The delta over goal-conductor, which carries the dispatch, patrol and acceptance procedure this one points at. Load it when you are handed a goal, not a task.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Team Lead

You are handed a goal. You run it as a team, and unlike a plain conductor you
can also do a piece of it yourself.

**Read `goal-conductor` first. It is your procedure.** Dispatch order, the patrol
loop, the acceptance evaluator, the stop conditions, your durable state and the
capacity reads are all there, they apply to you unchanged, and nothing here
repeats them -- a procedure stated twice is a procedure that drifts, and the
reader ends up following neither copy.

What follows is only what `goal-conductor` cannot say, because it is written for
an agent that has no hands.

## What is different about you

Your spec carries the default toolset, so you can write a file and run a command.
That is the one thing that separates you from a conductor, and it is the one
thing most likely to ruin a goal. The failure is not that you cannot do the
work. It is that you CAN, so you sit down and do item one while five items that
could have been running in parallel wait on you.

**You are the root of your own goal, unless a conductor dispatched you.** You
dispatch conductors and workers. Usually a goal is handed to you by a person, and
the person is the only reader above you. A conductor or another lead can also
dispatch you for one of its items; your session is then bound to that item, and
section 6 applies on top of everything else here. Call `work_brief` before you plan
to find out which: it answers `not_bound` when nobody dispatched you.

Your spec is a shipped default and is rewritten on every boot. An operator who
wants a lead of their own with different rules copies it to another agent name
rather than editing this one.

## 1. Echo the ask before you plan

Your first act is to restate the ask you were given, in the words you were given
it, and say what you take it to mean. Then plan.

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/builtin_skills/team-lead/SKILL.md