run-kit
/run-kit
Opisuje, jak prowadzić zespół techniczny: role, przebieg poleceń, pisanie briefu i przekazania między agentami w przestrzeni .team.
- Autor
- Tuan-Quyen ↗
- Repozytorium
- technical-teams ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Opisuje, jak prowadzić zespół techniczny: role, przebieg poleceń, pisanie briefu i przekazania między agentami w przestrzeni .team.
Oryginalny opis (EN)
Reference for running the technical team — the roster (who does what, writes what), the pipeline workflow commands, how to write a brief, the .team/ workspace with its templates, and the handoff every agent returns. Load it when running a pipeline, writing a brief, reading a handoff, or when the user asks what the team or a command does.
Jak działa
- 1. Roster
- 2. Pipeline workflow commands
- 3. Writing a brief
- 4. Workspace .team/
- 5. Handoff
Podgląd SKILL.md
---
name: run-kit
description: Reference for running the technical team — the roster (who does what, writes what), the pipeline workflow commands, how to write a brief, the .team/ workspace with its templates, and the handoff every agent returns. Load it when running a pipeline, writing a brief, reading a handoff, or when the user asks what the team or a command does.
---
# technical-team run kit
## 1. Roster
| Agent (`technical-team:…`) | Does | Writes | Badge |
|---|---|---|---|
| `team-lead` | classifies a request, runs the pipeline, keeps the resume point | `STATE.md`, moves into `archive/` | 🟪 🧭 |
| `team-ba` | requirements: stories, Given/When/Then ACs, edge cases, open questions | `requirements/<slug>.md`, `PRODUCT.md` | 🩵 🔍 |
| `team-designer` | design system, flows, screens, every state, copy | `frontend-design/DESIGN.md`, `frontend-design/<slug>.md` | 🩷 🎨 |
| `team-architect` | solution + implementation plan, architecture overview, ADRs | `system-design/<slug>.md`, `ARCHITECTURE.md`, `adr/` | 🟦 📐 |
| `team-pm` | tickets, dependencies, parallel groups, milestones, ticket status | `TASKS.md` | 🟨 📋 |
| `team-developer` | code changes per ticket or debug report, self-check | source code, config | 🟩 🛠️ |
| `team-debugger` | reproduce, root cause with evidence, fix direction | `reports/<slug>/debug.md` | 🟧 🐞 |
| `team-code-reviewer` | review the diff, PASS / FAIL | `reports/<slug>/review.md` | 🟥 👓 |
| `team-qa` | test plan, RTM, tests, live preview, PASS / FAIL | test files, `reports/<slug>/qa.md` | 🟨 🧪 |
| `team-security` | vulnerability review of a diff or the repo, PASS / FAIL | `reports/<slug>/security.md` | 🟥 🛡️ |
| `team-dba` | zero-downtime migrations, local/test databases only | migrations, "Data and migrations" in `system-design/<slug>.md` | 🟦 🗄️ |
| `team-devops` | CI/CD, Docker, manifests, local verification, remote steps for the user | infra files | 🟩 🚢 |
| `team-writer` | README, API docs, CHANGELOG, runbooks | product docs, `docs/**` | 🩵 ✍️ |
Paths are under `.team/`. Only the agent in the Writes column writes a file; everyone reads. Badge = default color and emoji; `.team/CREW.md` can override emoji, name, vibe and color per project (`/technical-team:crew`).
**Project specialists** — agents the project defines in `.claude/agents/*.md` (e.g. `prisma-expert`, `payments-reviewer`). The lead lists them at start, matches a step to one by its `description`, and either lets it **replace** the team agent for that step or **consults** it first (`team-lead.md` § Project specialists). They may declare `mcpServers`, `hooks` and `permissionMode`, which plugin agents cannot; that is the reason to write one instead of a project skill.
## 2. Pipeline workflow commands
`→` sequential, `∥` parallel. Each command file lists its steps; this is the map.
| Command | For | Pipeline | Stops for the user at |
|---|---|---|---|
| `feature` | a new capability or behaviour change | ba → designer (UI) → architect (+dba) → pm → developer → code-reviewer ∥ security → qa → writer | ba questions, design OK |
| `feature --small` | a change that fits existing patterns | developer → code-reviewer → qa | — |
| `fix` | a bug, error, failing test | debugger → developer → code-reviewer (∥ security) → qa | risky fix options |
| `review` | a diff, branch or range; no code changes | code-reviewer ∥ security (∥ dba) | — |
| `test` | missing tests for a scope | qa | — |
| `infra` | CI/CD, Docker, deploy | devops (proposal) → devops → code-reviewer ∥ security → writer | proposal OK |
| `release` | release readiness, GO / NO-GO | qa ∥ security ∥ devops (∥ dba) → writer | — |
| `new` | a product from an idea or PRD | ba → architect ∥ designer → architect → pm → per milestone: developer → review → qa → devops → writer → release | ba questions, stack, milestones |
Loops: review or QA `FAIL` → back to the developer with the finding IDs, then review again. Unclear failure → debugger. Design looks wrong → architect. Same findings after 3 rounds → ask the user.
## 3. Writing a brief
Every agent starts cold and sees only the brief. Give it:
```
Item: <slug> · Pipeline: <name> · Step: <n — name> · Ticket: <T-n or –>
Goal: <what this step must produce>
Read: <the .team/ files and code paths it needs>
Write: <the files it owns for this step>
Constraints: <scope, user decisions so far, finding IDs to fix, ADR number if any, MCP tools / project skills to use and which outside changes the user allowed>
User's language: <language>
```
- Name files, not "the findings above": the agent cannot see the conversation.
- Pass user answers verbatim.
- Parallel agents never share a file in **Write**.
**Briefing a project specialist** — it has none of the team's Rules, so the brief carries them. Use the format above, then add:
```
Rules: write only the files under Write (none = advise only). Never write .team/STATE.md, never commit or push.
Reading MCP is free; an outside change only if Constraints says the user allowed it.
Reply ending: the Handoff block of §5 (use your name; emoji ⬜).
```
## 4. Workspace `.team/`
| File | Owner | Template (`${CLAUDE_PLUGIN_ROOT}/templates/…`) |
|---|---|---|
| `STATE.md` — who works on what, files in use, next step (resume point) | lead | `core/STATE.md` |
| `TASKS.md` — tickets and status | pm | `core/TASKS.md` |
| `PRODUCT.md` — current truth of the product | ba | `core/PRODUCT.md` |
| `ARCHITECTURE.md` — overview, ~200 lines max, points to ADRs | architect | `core/ARCHITECTURE.md` |
| `requirements/<slug>.md` | ba | `requirements/requirements.md` |
| `system-design/<slug>.md` — design + implementation plan | architect (dba: Data and migrations) | `design/system-design.md` |
| `frontend-design/DESIGN.md` — design system | designer | `design/DESIGN.md` |
| `frontend-design/<slug>.md` | designer | `design/frontend-design.md` |
| `adr/NNNN-<decision>.md` — NNNN given by the lead | architect | `adr/adr.md` |
| `reports/<slug>/qa.md` — plan → RTM → findings → latest round → verdict | qa | `reports/qa.md` |
| `reports/<slug>/review.md` | code-reviewer | `reports/review.md` |
| `reports/<slug>/security.md` | security | `reports/security.md` |
| `reports/<slug>/debug.md` | debugger | `reports/debug.md` |
| `CREW.md` — emoji, names, vibes, badge colors (optional) | lead, on the user's instruction | `core/CREW.md` |
| `docs/**` | writer | — |
| `archive/<slug>/` — every file of a closed item | lead | — |
Reports keep a cumulative findings table with fixed IDs (`Q-01`, `R-01`, `S-01`) and only the latest round in detail; line 1 is the verdict.
## 5. Handoff
Every agent opens its reply with `<emoji> <name>:` and ends it with:
```
### Handoff · <emoji> <name>
- Status: done | blocked | needs-input
- Files: <created / changed, or "none">
- Evidence: <commands run and their result, or "none">
- Next: <agent or "user"> — <what>
```
| Status | Means | Next move |
|---|---|---|
| `done` | step finished, evidence attached | next step of the pipeline (no evidence → treat as `blocked`) |
| `blocked` | cannot continue | debugger for an unclear failure, architect for a design problem, otherwise the user |
| `needs-input` | a decision belongs to the user | ask the user, pass the answer back verbatim |
Wersje
W bazie nie ma innych skilli o nazwie run-kit.
Migawka bazy z 13.11.2026 · wersja paczki df7896c3a5a3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100build-agent-team
Projektuje długo działający, autonomiczny zespół agentów Claude Code dla bieżącego projektu i zapisuje skill /start-nazwa-team, który go uruchamia ze wspólnymi zadaniami i komunikacją między agentami. - 96team-coding-workflow
Buduje potok zespołu kodującego z wieloma rolami AI, z etapami i przekazaniami między nimi. - 90atdd-team
Koordynuje zespół agentów w sześciu fazach ATDD: pisanie i przegląd specyfikacji, potok testów, implementacja, poprawki i weryfikacja. - 96context-acquisition
Przejmuje kontekst z briefu przekazania na początku sesji i czyta go jednorazowo. - 100multi-agent-handoff-prompt-protocols
Projektuje jawne kontrakty przekazania kontekstu i zakończenia zadań między wyspecjalizowanymi agentami AI. - 100multi-agent-team-designer
Projektuje zespół trzech do pięciu agentów AI do procesu biznesowego: role, prompty, przekazania i siedmiodniowy plan wdrożenia.