team-build — скилл для Claude Code: что делает и как установить
Скилл team-build для Claude Code задаёт регламент TDD: цикл red-green-refactor, фиксацию швов тестирования и проверку критериев приёмки перед сдачей в QA.
MIT ★ 71 обновлён 2026-11-13
npx skills add sametcelikbicak/opencode-team --skill team-build -a claude-codeЧто делает team-build
Скилл ведёт разработку через TDD мелкими вертикальными срезами. Перед тестами агент читает тикет в .team/03-backlog.md и контракт в .team/06-architecture.md. Каждый шаг цикла состоит из одного падающего теста, минимальной реализации и рефакторинга без смены публичного интерфейса.
Проверка поведения идёт строго по внешним границам — швам (seams), список которых заранее согласовывается. Пирамида тестов распределяет нагрузку на 70% юнит-тестов, 20% интеграционных и 10% сквозных (e2e). Тесты изолируются: внешние зависимости подменяются моками только на границах, случайность сидируется, а время фиксируется фейковыми часами.
Сборка завершена, когда каждый критерий приёмки покрыт проверенным тестом и сформирован отчёт .team/07-build-fe.md или .team/07-build-be.md. Если рефакторинг задевает модель данных или API, агент передаёт задачу ветке team-architecture.
Какие задачи решает
- настроить цикл TDD по схеме red-green-refactor
- согласовать границы тестирования (seams) до написания кода
- устранить нестабильные тесты с сетевыми вызовами и плавающим временем
- подготовить отчёт о сборке перед передачей этапа в QA
Примеры запросов агенту
- Напиши падающий юнит-тест на критерий приёмки из
.team/03-backlog.md - Согласуй швы для модуля оплаты и напиши минимальный код под зелёный тест
- Сделай рефакторинг без изменения контракта и составь отчёт
.team/07-build-be.md
Как установить team-build
1Через Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-build -a claude-code2Вручную: положить файлы
~/.claude/skills/team-build/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/team-build/
1Через Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-build -a codex2Вручную: положить файлы
.agents/skills/team-build/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-build -a cursor2Вручную: положить файлы
.cursor/skills/team-build/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install sametcelikbicak/opencode-team skills/team-build2Вручную: положить файлы
.github/skills/team-build/SKILL.md1Через Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-build -a gemini-cli2Командой платформы
gemini skills install https://github.com/sametcelikbicak/opencode-team --path skills/team-buildВручную: положить файлы
.devin/skills/team-build/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о team-build
Как установить team-build в Claude Code?
Запустите команду npx skills add sametcelikbicak/opencode-team --skill team-build -a claude-code в терминале. Также можно сохранить файл навыка по пути ~/.claude/skills/team-build/SKILL.md.
Что делает team-build?
Он задаёт правила тестирования по TDD: прогон цикла red-green-refactor, проверку поведения через публичные интерфейсы, соблюдение пропорций пирамиды тестов и оформление отчёта для QA.
Что нужно для работы team-build?
Нужны файлы задачи .team/03-backlog.md и архитектурного контракта .team/06-architecture.md. При изменении структуры модулей требуется смежный скилл team-architecture.
Исходный текст
SKILL.md · MIT
--- name: team-build description: The build and TDD playbook for this team. Red-green-refactor, test-first vertical slices, seams, test pyramid, mocking at boundaries, deterministic tests and definition of done. --- # Build: Test-Driven Development TDD is the **red → green → refactor** loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, what to mock, how to keep tests deterministic, and when the build is done. Read [tests.md](tests.md) for examples and [mocking.md](mocking.md) for boundary guidelines. Before the first test, read the ticket in `.team/03-backlog.md` and the contract in `.team/06-architecture.md`. The acceptance criteria and the API contract are the source of truth, not the implementation you are about to write. Use the project's domain vocabulary so test names match the product language. ## The loop 1. **Red** — write one failing test for one acceptance criterion. Run it and see it fail for the right reason. 2. **Green** — write only enough code to pass that test. Do not anticipate the next test or add speculative features. 3. **Refactor** — with the test still green, remove duplication in the production code and the test. Keep the public contract unchanged. One seam, one test, one minimal implementation per cycle. If a refactor changes module boundaries, the API contract or the data model, stop: that is an architecture change for the `team-architecture` skill ([SKILL.md](../team-architecture/SKILL.md)) and belongs in the next cycle, not hidden inside a green step. ## What a good test is Tests verify **behavior through public interfaces**, not implementation details. Code can change entirely; tests should not. A good test reads like a specification: "user can checkout with valid cart" tells you exactly what capability exists, and it survives refactors because it does not care about internal structure. A test is the verification of an acceptance criterion, not proof that a line of code ran. Coverage percentage is not the goal; reliability is. See [tests.md](tests.md) for good and bad examples. ## Seams: where tests go A **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals. Test only at pre-agreed seams. Before writing tests, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You cannot test everything, so agreeing the seams up front is how testing effort lands on critical paths and complex logic instead of every edge case. Ask: "What is the public interface, and which seams should we test?" Give each proposed seam a one-line note on what it catches and what it misses. When the shape of that interface is itself in question — how deep the module is, where the seam belongs, what it should expose — consult the `team-architecture` skill ([SKILL.md](../team-architecture/SKILL.md)). Its module boundaries and API contract define the seams; do not invent a second interface just for tests. ## The test pyramid | Type | What it tests | Ratio | Speed | |---|---|---|---| | Unit | Business logic, edge cases | 70% | ms | | Integration | DB, API, file system, external boundary adapters | 20% | s | | e2e | The user journey | 10% | s–min | Do not write e2e for everything. e2e is fragile and slow; use it only for the main journeys that bring in money. ## Anti-patterns - **Implementation-coupled**: mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior has not changed. - **Tautological**: the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth: a known-good literal, a worked example, the spec. - **Horizontal slicing**: writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead: one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you. - **Weakening the test**: deleting or loosening an assertion to make a test pass. See "Definition of done". ## Deterministic tests A test that depends on the clock, the network, random data or execution order is a flaky test. Flaky tests train the team to ignore red. - Fix time with the test framework's fake clock, or inject a clock. Never assert against `Date.now()`. - Seed randomness, or inject the random source. - Mock only the external boundary (see [mocking.md](mocking.md)); never reach the real network in a unit test. - Each test creates its own state and cleans it up. Tests must pass in any order and in parallel where the runner allows. - Do not hide a race condition by raising a timeout. Fix the cause or mark the test as an explicit known issue. ## Definition of done The build is done only when all of these are true: - Every acceptance criterion in the ticket has at least one test that maps to it. - Each test was seen failing before the implementation that made it pass. - The full suite passes, deterministically, in the project's configured command. - No test was skipped, deleted, loosened or given a longer timeout to get green. - Tests are versioned next to the code they verify. - No known failing case is hidden. If something cannot be tested, say why in the build report. ## Handoff to QA After implementation and tests are green, write your specialist report — `.team/07-build-fe.md` for frontend, `.team/07-build-be.md` for backend: - What was built, per ticket and per acceptance criterion. - Tests added, with the criterion each one covers. - Exact commands run and their exact output (or "not run"). - Known gaps, shortcuts and risks. The orchestrator consolidates the specialist reports into `.team/07-build.md` after every requested specialist has completed successfully. Do not write the consolidated report yourself. Then hand off to the **QA stage**: the `qa` agent ([agents/qa.md](../../agents/qa.md)) reads `.team/06-architecture.md` and `.team/07-build.md`, follows the `team-qa` skill ([SKILL.md](../team-qa/SKILL.md)), and independently verifies the acceptance criteria. Do not report the QA stage as passed from the build stage; only QA can do that. > Adapted from the MIT-licensed test-driven development skill by Matt Pocock. See THIRD_PARTY_NOTICES.md.
© sametcelikbicak · MIT · sametcelikbicak/opencode-team