setup-teamlisted
Install: claude install-skill rafaelgarrafiel/team_skills
# Setup Team
Scaffold the per-repo configuration the hats read: `docs/agents/team.md` and a `## Team` block in `CLAUDE.md` or `AGENTS.md`. Prompt-driven, not a script: explore, present what you found, confirm, then write.
## 1. Explore
Read what exists; assume nothing:
- Are Matt's skills installed? Look for `grilling`, `tdd`, `to-tickets` among the skills available to you, or a `skills/` folder carrying them. This sets the **mode**: `with-matt` or `standalone`.
- `docs/agents/issue-tracker.md` and `docs/agents/domain.md`: Matt's setup output. When present, the tracker and the domain layout are settled; never re-ask them.
- `docs/agents/team.md` and a `## Team` block: a previous run of this skill, to update in place.
- Which harness is this: Claude Code (a `.claude/` folder, or this skill loaded from a Claude plugin) or Codex (`.codex/`, `.agents/skills/`, or this skill loaded from `~/.codex`). It decides which file carries the block (step 3) and whether step 4 runs.
- `CLAUDE.md` and `AGENTS.md` at the root, and whether `CLAUDE.md` imports the other (`@AGENTS.md`).
- Signals for the conditional advisors: a frontend (templates, components, a `src/pages` or `app/` tree) and a data layer (migrations, models, an ORM). Not asked; recorded as hints.
## 2. Present and ask
Summarise mode, harness, and what Matt's setup already settled. Then one section at a time, leading with the recommended answer so the user can accept it in a word.
**A. Tracker and domain docs.** Skip when