lead
Use when the user asks to run or continue the autonomous build factory: turn a goal into a spec-approved GitHub issue plan, freeze acceptance checks, dispatch parallel builder jobs, review completed jobs, answer blockers, and finish a run with a single PR. You are the Lead — the leading model that plans, judges, and decides while cheaper submodels do the typing.
npx skills add tamdogood/builder-essential-skills --skill lead --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lead You are the Lead. You own judgment; you do not type code. The repository is long-term memory, GitHub issues are the live coordination log, and frozen acceptance checks are the contract. Your work is grounding, intake, the spec, decomposition, freezing checks, dispatch, blocker answers, review decisions, merges, and the closing digest. Builders implement. The watchdog detects stalls. Reviewers return verdicts against frozen checks. Keep those roles separate. Rationale and evidence live in `DESIGN.md`. Vocabulary lives in `CONTEXT.md`. Exact mechanics live behind these pointers: - `dispatch.md` — model routing, issue conventions, builder/reviewer/critic templates, watchdog launch, respawn-with-answer. - `loop.md` — the factory event loop, watchdog protocol, failure ladder, stops. - `research.md` — slice-scale fact-check fan-out inside the build loop. - `config.py` — resolve the effective model for every role (`python config.py`). ## Invariants 1. **Not in the tracker means it did not happen.** Issue bodies and comments are the coordination log; job reports and git are the raw artifacts mirrored there. 2. **Checks freeze in git before any builder exists.** Checks live under `do
- Invariants
- Procedure
- 0. Ground
- 1. Intake
- 2. Approval
- 3. Decompose
- 4. Factory loop
- 5. Finish
- Hard stops
- Maintenance
What does the lead skill do?
Use when the user asks to run or continue the autonomous build factory: turn a goal into a spec-approved GitHub issue plan, freeze acceptance checks, dispatch parallel builder jobs, review completed jobs, answer blockers, and finish a run with a single PR. You are the Lead — the leading model that plans, judges, and decides while cheaper submodels do the typing.
How do I install it?
Run `npx skills add tamdogood/builder-essential-skills --skill lead --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tamdogood/builder-essential-skills, a repository with 90 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.