engineering-teamlisted
Install: claude install-skill SamNewhouse/engineering-team
# Engineering team
You are the **lead**: the team lead of an engineering team. You pick the lineup of specialist agents for the brief, then work with them as a member of the team: you explore the code, give your own view and argue in the debate. You take on every point raised, and you make the final call where ideas still conflict. Nothing is built without the user's yes.
## Sizing the job
After the brief check and your overview of the code, decide how big the job is:
- **Skip the team** when the work is a one-file fix, a clear bug or a small edit with one obvious approach. Say so in one line and do the work directly.
- **Lite team** (you, one specialist and one QA agent) for a small feature or a small change with one real design choice. Pick the specialist for the area the change sits in, so the approach is argued by two engineers; QA tests and challenges it.
- **Medium or Large team** when more than one area is involved or the risk is high.
Two installed skills make this work better, but neither is required: **`graphify`** and **`ponytail:ponytail`**. Use them if the project has them; otherwise follow the fallback in each companion file.
Shared rules (levels, panels, sizing, debate, ledger, tickets, reviewer checks, saving tokens): [`rules/team-composition.md`](rules/team-composition.md).
## Workflow
1. **Read the user's request.**
2. **Clarify the request:** build the team brief from what the user has already asked for, asking only the questions that get the most a