@bonesofspring/ai-rules 0.2.14 → 0.2.16

package/presets/cursor/android-kotlin/team/fixtures/bugfix-standard.json

@@ -0,0 +1,47 @@
+{
+  "slug": "example-bugfix-standard",
+  "intent": "bugfix",
+  "profile": "standard",
+  "summary": "Bugfix with unit coverage and optional instrumentation",
+  "steps": [
+    {
+      "agent": "task-analyst",
+      "label": "Clarify repro and AC"
+    },
+    {
+      "agent": "debugger",
+      "label": "Reproduce and locate root cause"
+    },
+    {
+      "agent": "feature-developer",
+      "label": "Minimal fix + unit test",
+      "scope": "unit-in-dev"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "Gradle compile + lint + unit smoke",
+      "model": "cheap"
+    },
+    {
+      "agent": "code-reviewer",
+      "label": "Code review",
+      "model": "cheap"
+    }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "playwright-test-planner",
+      "reason": "Android uses instrumentation-test-*"
+    },
+    {
+      "agent": "xcuitest-test-planner",
+      "reason": "iOS-only"
+    },
+    {
+      "agent": "instrumentation-test-planner",
+      "reason": "No UI AC \u2014 add if regression is UI-only"
+    }
+  ]
+}

package/presets/cursor/android-kotlin/team/fixtures/feature-full.json

@@ -0,0 +1,97 @@
+{
+  "slug": "example-feature-full",
+  "intent": "feature",
+  "profile": "full",
+  "summary": "Multi-layer feature with Android instrumentation coverage",
+  "steps": [
+    {
+      "agent": "task-analyst",
+      "label": "Clarify and decompose"
+    },
+    {
+      "agent": "solution-architect",
+      "label": "Design boundaries",
+      "model": "strong"
+    },
+    {
+      "agent": "feature-developer",
+      "label": "Implement + unit tests",
+      "scope": "unit-in-dev"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "Gradle compile + lint + unit smoke",
+      "model": "cheap"
+    },
+    {
+      "agent": "security-reviewer",
+      "label": "Security review",
+      "model": "strong"
+    },
+    {
+      "agent": "code-reviewer",
+      "label": "Code review",
+      "model": "cheap"
+    },
+    {
+      "agent": "accessibility-reviewer",
+      "label": "Compose a11y",
+      "model": "cheap"
+    },
+    {
+      "agent": "instrumentation-test-planner",
+      "label": "Plan instrumentation UI tests"
+    },
+    {
+      "agent": "instrumentation-test-generator",
+      "label": "Generate instrumentation tests"
+    },
+    {
+      "agent": "instrumentation-test-healer",
+      "label": "Heal flaky instrumentation",
+      "model": "cheap"
+    }
+  ],
+  "humanGates": [
+    "after:task-analyst"
+  ],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "playwright-test-planner",
+      "reason": "Android uses instrumentation-test-* \u2014 not Playwright"
+    },
+    {
+      "agent": "playwright-test-generator",
+      "reason": "Android uses instrumentation-test-*"
+    },
+    {
+      "agent": "playwright-test-healer",
+      "reason": "Android uses instrumentation-test-*"
+    },
+    {
+      "agent": "xcuitest-test-planner",
+      "reason": "iOS-only"
+    },
+    {
+      "agent": "xcuitest-test-generator",
+      "reason": "iOS-only"
+    },
+    {
+      "agent": "xcuitest-test-healer",
+      "reason": "iOS-only"
+    },
+    {
+      "agent": "integration-test-planner",
+      "reason": "JVM backend pattern \u2014 not Android UI"
+    },
+    {
+      "agent": "integration-test-generator",
+      "reason": "JVM backend pattern"
+    },
+    {
+      "agent": "integration-test-healer",
+      "reason": "JVM backend pattern"
+    }
+  ]
+}

package/presets/cursor/android-kotlin/team/fixtures/feature-light.json

@@ -0,0 +1,38 @@
+{
+  "slug": "example-feature-light",
+  "intent": "feature",
+  "profile": "light",
+  "summary": "Trivial single-file change with explicit AC",
+  "steps": [
+    {
+      "agent": "feature-developer",
+      "label": "Implement",
+      "model": "cheap"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "Gradle compile + lint + unit smoke",
+      "model": "cheap"
+    }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "task-analyst",
+      "reason": "Explicit AC and single-file scope"
+    },
+    {
+      "agent": "code-reviewer",
+      "reason": "Light profile \u2014 non-trivial app changes should use standard"
+    },
+    {
+      "agent": "instrumentation-test-planner",
+      "reason": "No UI AC"
+    },
+    {
+      "agent": "playwright-test-planner",
+      "reason": "Android uses instrumentation-test-*"
+    }
+  ]
+}

package/presets/cursor/go/AGENTS.md

@@ -2,16 +2,16 @@
 
 **Repo-root agents:** see [`AGENTS.md`](../../AGENTS.md) at the project root (cross-tool setup, commands, security, living conventions pointers).
 
-| Задача | Куда смотреть |
+| Task | Where to look |
 |--------|----------------|
-| Новая work-задача | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
-| Фича end-to-end | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
-| Стек и слои | `go-app-core.mdc`, `architecture-boundaries.mdc` |
-| После правок Go | `post-change-test.mdc` (+ `go-tooling.mdc`) |
+| New work task | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
+| Feature end-to-end | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
+| Stack and layers | `go-app-core.mdc`, `architecture-boundaries.mdc` |
+| After Go edits | `post-change-test.mdc` (+ `go-tooling.mdc`) |
 | Integration tests | `integration-test-*` + skill `integration-testing` |
 | Code review | skill `code-review` + `code-review-mr.mdc` |
 | ADR | skill `write-adr` (on-demand) |
-| Как работает X | agent `codebase-analyzer` (explain-as-is; без `/task`) |
+| How does X work | agent `codebase-analyzer` (explain-as-is; without `/task`) |
 
 ## Install
 
@@ -19,12 +19,12 @@
 npx @bonesofspring/ai-rules init cursor --preset go
 ```
 
-Копирует rules/agents/hooks/skills/team + `REPO_AGENTS.md` → корневой `AGENTS.md`.
+Copies rules/agents/hooks/skills/team + `REPO_AGENTS.md` → root `AGENTS.md`.
 
-## Dogfood (5 сценариев)
+## Dogfood (5 scenarios)
 
-1. `/task` — новый use case (domain → ports → adapters → wire).
-2. Баг маппинга HTTP — debugger + httptest.
+1. `/task` — new use case (domain → ports → adapters → wire).
+2. HTTP mapping bug — debugger + httptest.
 3. Repository contract — integration-test trio.
 4. Unit use case — unit-test planner/generator.
 5. Secrets in logs — security-reviewer + `security-go`.

package/presets/cursor/go/MCP.md

@@ -1,16 +1,16 @@
 # MCP (preset `go`, Cursor)
 
-Копируется в `.cursor/mcp.json` при `ai-rules init cursor --preset go`.
+Copied to `.cursor/mcp.json` on `ai-rules init cursor --preset go`.
 
 ## Servers
 
-| Name | Package | Зачем |
+| Name | Package | Why |
 |------|---------|--------|
-| `context7` | `@upstash/context7-mcp` | Актуальная документация Go / stdlib / популярных библиотек |
-| `figma` | remote `https://mcp.figma.com/mcp` | Design context при необходимости; OAuth в Cursor |
+| `context7` | `@upstash/context7-mcp` | Up-to-date Go / stdlib / popular library docs |
+| `figma` | remote `https://mcp.figma.com/mcp` | Design context when needed; OAuth in Cursor |
 
-Browser e2e MCP (Playwright / Chrome DevTools) **не** входят в go-пресет.
+Browser e2e MCP (Playwright / Chrome DevTools) are **not** part of the go preset.
 
-Секреты в файл не кладём. Опционально: `CONTEXT7_API_KEY` в окружении. Figma — OAuth (токен не коммитим).
+Do not put secrets in the file. Optional: `CONTEXT7_API_KEY` in the environment. Figma — OAuth (do not commit the token).
 
-После init: Settings → MCP → включить серверы. `init` перезаписывает одноимённый `mcp.json`.
+After init: Settings → MCP → enable servers. `init` overwrites the same-named `mcp.json`.

package/presets/cursor/go/README.md

@@ -1,6 +1,6 @@
 # Go hexagonal preset (Cursor)
 
-Правила и agent-team surface для Go backend (hexagonal / ports & adapters).
+Rules and agent-team surface for Go backends (hexagonal / ports & adapters).
 
 ## Install
 
@@ -8,13 +8,13 @@
 npx @bonesofspring/ai-rules init cursor --preset go
 ```
 
-| Path | Содержание |
+| Path | Contents |
 |------|------------|
 | `REPO_AGENTS.md` | → repo-root `AGENTS.md` (cross-tool) |
 | `AGENTS.md` | → `.cursor/AGENTS.md` quick-start |
 | `BUGBOT.md` | Bugbot review priorities (Go) |
 | `rules/**` | `.mdc` + README (alwaysApply ≤3) |
-| `agents/**` | **21** ролей (+ README; includes on-demand `codebase-analyzer`) |
+| `agents/**` | **21** roles (+ README; includes on-demand `codebase-analyzer`) |
 | `skills/**` | **8** skills (incl. `integration-testing`, `write-adr`; no `react-performance`) |
 | `commands/**` | task, task-continue, feature-start/continue, technical-retro |
 | `hooks.json` + `hooks/**` | guard-shell + chain-team-phases; optional `hooks/examples/` |
@@ -36,4 +36,4 @@ Requestable: `post-change-test`, `go-tooling`, `agent-team-*`, hexagonal layer g
 
 ## Sync with Claude
 
-SoT = этот Cursor-пресет. Twin: `presets/claude/go/` **в том же PR**.
+SoT = this Cursor preset. Twin: `presets/claude/go/` **in the same PR**.

package/presets/cursor/go/agents/README.md

@@ -1,10 +1,10 @@
 # `.cursor/agents` (preset go)
 
-Ролевые subagents для командного пайплайна Cursor (Go hexagonal).
+Role subagents for the Cursor agent-team pipeline (Go hexagonal).
 
 ## Analysis (on-demand)
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | Codebase analyzer | `codebase-analyzer.md` | no (explain-as-is only) |
 
@@ -25,7 +25,7 @@
 
 ## Frontmatter `readonly`
 
-Все agents — **`readonly: false`** (нужна запись в `.cursor/team/**`). Ограничения production — в теле промпта.
+All agents are **`readonly: false`** (need write access to `.cursor/team/**`). Production constraints are in the prompt body.
 
 ## Model matrix (frontmatter `model`)
 

package/presets/cursor/go/agents/task-router.md

@@ -17,21 +17,21 @@ You are a task router for a **Go hexagonal backend** agent team. You **do not**
 
 | intent | Signals | Default steps |
 |--------|---------|---------------|
-| `feature` | «добавь», «новая», «реализуй», use case/API/adapter | task-analyst → feature-developer → build-verifier → code-reviewer → qa-tester or **integration-test** trio when adapter AC |
-| `bugfix` | «баг», «fix», «не работает», «падает» | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer |
-| `ci-fix` | «CI», «красный PR», «failing check» | ci-investigator → feature-developer (skipIf resolved) → build-verifier → code-reviewer |
-| `migration` | «миграция», «upgrade», «обнови Go/module» | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer |
-| `perf-audit` | «производительность», «pprof», «медленно» | performance-auditor |
-| `review-only` | «ревью», «review MR», «проверь diff» | code-reviewer |
-| `test-only` | «покрой тестами» (unit+integration, no impl) | task-analyst → qa-tester |
-| `unit-only` | «unit», «юнит», «покрой use case» | unit-test-planner → unit-test-generator, or unit-test-healer |
+| `feature` | «добавь» (add), «новая» (new), «реализуй» (implement), use case/API/adapter | task-analyst → feature-developer → build-verifier → code-reviewer → qa-tester or **integration-test** trio when adapter AC | <!-- i18n-keep: E4 -->
+| `bugfix` | «баг» (bug), «fix», «не работает» (doesn't work), «падает» (crashes) | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `ci-fix` | «CI», «красный PR» (red PR), «failing check» | ci-investigator → feature-developer (skipIf resolved) → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `migration` | «миграция» (migration), «обнови Go/module» (upgrade), "update Go/module" | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `perf-audit` | «производительность» (performance), «pprof», «медленно» (slow) | performance-auditor | <!-- i18n-keep: E4 -->
+| `review-only` | «ревью» (review), «проверь diff» (review MR), "check diff" | code-reviewer | <!-- i18n-keep: E4 -->
+| `test-only` | «покрой тестами» (cover with tests), (unit+integration, no impl) | task-analyst → qa-tester | <!-- i18n-keep: E4 -->
+| `unit-only` | «юнит» (unit), «покрой use case» (cover use case) | unit-test-planner → unit-test-generator, or unit-test-healer | <!-- i18n-keep: E4 -->
 | `e2e-only` / integration | «integration», «e2e», «httptest», «testcontainers» | **integration-test-planner** → **integration-test-generator**, or **integration-test-healer** |
-| `docs-only` | «документация», «README», «changelog» | task-analyst → tech-writer |
-| `refactor` | «рефакторинг», «без изменения поведения» | task-analyst → feature-developer → build-verifier → code-reviewer |
-| `spike` | «исследуй», «spike», proof of concept | task-analyst → solution-architect |
-| `retro` | «ретро», «postmortem» | (orchestrator → `/technical-retro`) |
+| `docs-only` | «документация» (docs), "README", "changelog" | task-analyst → tech-writer | <!-- i18n-keep: E4 -->
+| `refactor` | «рефакторинг» (refactor), «без изменения поведения» (no behavior change) | task-analyst → feature-developer → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `spike` | «исследуй» (explore), "spike", proof of concept | task-analyst → solution-architect | <!-- i18n-keep: E4 -->
+| `retro` | «ретро» (retro), "postmortem" | (orchestrator → `/technical-retro`) | <!-- i18n-keep: E4 -->
 
-**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), or `accessibility-reviewer`. Put them in `skipped` with reason «Go backend uses integration-test trio».
+**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), or `accessibility-reviewer`. Put them in `skipped` with reason "Go backend uses integration-test trio".
 
 ## Pipeline profiles
 

package/presets/cursor/go/commands/README.md

@@ -1,54 +1,54 @@
 # Cursor commands (go preset)
 
-Slash-команды копируются в `.cursor/commands/` при `ai-rules init cursor --preset go`.
+Slash commands are copied to `.cursor/commands/` on `ai-rules init cursor --preset go`.
 
-## Команда агентов
+## Agent commands
 
-| Command | Назначение |
+| Command | Purpose |
 |---------|------------|
-| **`/task <описание>`** | **Главная точка входа:** router → pipeline.json → нужные роли по порядку |
-| `/task-continue <slug>` | После human gate или паузы |
-| `/feature-start <описание>` | Legacy: только analyst (без router) |
+| **`/task <description>`** | **Main entry point:** router → pipeline.json → required roles in order |
+| `/task-continue <slug>` | After a human gate or pause |
+| `/feature-start <description>` | Legacy: analyst only (no router) |
 | `/feature-continue <slug>` | Alias task-continue |
-| `/technical-retro [slug]` | Ретро; с slug — блок «Работа агентов» |
+| `/technical-retro [slug]` | Retro; with slug — “Agent work” block |
 
-## Примеры `/task`
+## `/task` examples
 
 ```
-/task Добавить CancelOrder use case (domain → ports → HTTP)
+/task Добавить CancelOrder use case (domain → ports → HTTP) (Add CancelOrder use case) <!-- i18n-keep: E4 -->
 → analyst → developer → build-verifier → reviewer → QA (integration)
 
-/task httptest CreateOrder падает на пустом body
+/task httptest CreateOrder падает на пустом body (httptest CreateOrder crashes on empty body) <!-- i18n-keep: E4 -->
 → debugger → developer → reviewer → QA (regression)
 
-/task CI упал на go test / golangci-lint в PR #142
+/task CI упал на go test / golangci-lint в PR #142 (CI failed on go test / golangci-lint in PR #142) <!-- i18n-keep: E4 -->
 → ci-investigator → developer → reviewer
 
-/task Миграция HTTP-роутера на chi v5
+/task Миграция HTTP-роутера на chi v5 (Migrate HTTP router to chi v5) <!-- i18n-keep: E4 -->
 → analyst → migration-specialist → developer → reviewer → QA
 
-/task Проверь OpenAPI drift для /orders
+/task Проверь OpenAPI drift для /orders (Check OpenAPI drift for /orders) <!-- i18n-keep: E4 -->
 → api-contract-reviewer (or analyst → …)
 
-/task Покрой unit-тестами CancelOrder use case
+/task Покрой unit-тестами CancelOrder use case (Cover CancelOrder use case with unit tests) <!-- i18n-keep: E4 -->
 → unit-planner → unit-generator
 
-/task Напиши README для нового adapter persistence
+/task Напиши README для нового adapter persistence (Write README for new persistence adapter) <!-- i18n-keep: E4 -->
 → analyst → tech-writer
 
-/task Сделай ревью изменений в internal/adapters/http
+/task Сделай ревью изменений в internal/adapters/http (Review changes in internal/adapters/http) <!-- i18n-keep: E4 -->
 → reviewer only
 
-/task Repository contract для OrderRepository
-→ integration-test-planner → generator → healer (или QA e2e-only = integration)
+/task Repository contract для OrderRepository (Repository contract for OrderRepository) <!-- i18n-keep: E4 -->
+→ integration-test-planner → generator → healer (or QA e2e-only = integration)
 ```
 
-## Связанные файлы
+## Related files
 
-- Subagents: `../agents/` (**21** ролей, включая `task-router.md`, `codebase-analyzer.md` и `integration-test-{planner,generator,healer}`; без `accessibility-reviewer` / Playwright / XCUITest)
-- Оркестратор: `../rules/agent-team-orchestrator.mdc`
+- Subagents: `../agents/` (**21** roles, including `task-router.md`, `codebase-analyzer.md`, and `integration-test-{planner,generator,healer}`; no `accessibility-reviewer` / Playwright / XCUITest)
+- Orchestrator: `../rules/agent-team-orchestrator.mdc`
 - Skills: `../skills/` (`feature-delivery`, `code-review`, `debug-investigation`, `ci-investigation`, `unit-testing`, `integration-testing`, `technical-retro`)
-- Артефакты: `../team/README.md` (`pipeline.json`, `status.json`)
+- Artifacts: `../team/README.md` (`pipeline.json`, `status.json`)
 - Hooks: `../hooks.json`, `../hooks/chain-team-phases.sh`
 
-Создавать и редактировать команды можно через `/commands` в Cursor или напрямую в этой папке пресета.
+Create and edit commands via `/commands` in Cursor or directly in this preset folder.

package/presets/cursor/go/commands/feature-continue.md

@@ -5,15 +5,15 @@ description: Legacy alias for /task-continue that resumes a feature pipeline aft
 
 # Feature continue — legacy alias
 
-> **Предпочтительно:** `/task-continue <slug>` — то же поведение, учитывает `pipeline.json`.
+> **Preferred:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
 
-Продолжение после human gate. Полная логика — в **`task-continue.md`**.
+Continue after a human gate. Full logic lives in **`task-continue.md`**.
 
-## Кратко
+## Short version
 
-1. Прочитай `pipeline.json` (если есть) и `status.json`.
-2. Сбрось `awaitingHumanGate`; определи следующий step по `pipelineIndex`.
-3. Вызови subagent для `currentAgent`.
-4. Hook продолжит цепочку при `autoChain: true`.
+1. Read `pipeline.json` (if present) and `status.json`.
+2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
+3. Call the subagent for `currentAgent`.
+4. The hook continues the chain when `autoChain: true`.
 
-См. `task-continue.md` для деталей и таблицы handoff.
+See `task-continue.md` for details and the handoff table.

package/presets/cursor/go/commands/feature-start.md

@@ -5,29 +5,29 @@ description: Legacy analyst-only feature intake. Prefer /task for new work becau
 
 # Feature start — legacy (analyst only)
 
-> **Предпочтительно:** `/task <описание>` — router выберет роли и порядок автоматически.
+> **Preferred:** `/task <description>` — the router picks roles and order automatically.
 
-Запуск **фазы анализа** без router. Родительский агент действует как оркестратор (см. `agent-team-orchestrator.mdc`).
+Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `agent-team-orchestrator.mdc`).
 
-## Что делать
+## What to do
 
-1. Извлеки описание задачи из аргументов команды (всё после `/feature-start`).
-2. Сгенерируй **slug** (kebab-case, до 48 символов) из заголовка задачи.
-3. Создай `.cursor/team/tasks/<slug>/` если его ещё нет — через **Write** артефакта (не Shell `mkdir`).
-4. Запиши `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Опционально: минимальный `pipeline.json` с фиксированными steps (analyst → developer → reviewer → qa-tester).
-6. Вызови subagent **task-analyst** (Task tool) с полным описанием задачи и путём к артефактам.
-7. Дождись завершения аналитика. **Не вызывай developer** на этом этапе.
+1. Extract the task description from command arguments (everything after `/feature-start`).
+2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
+3. Create `.cursor/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
+4. Write `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
+5. Optionally: minimal `pipeline.json` with fixed steps (analyst → developer → reviewer → qa-tester).
+6. Invoke subagent **task-analyst** (Task tool) with the full task description and artifact paths.
+7. Wait for the analyst to finish. **Do not invoke developer** at this stage.
 
 ## Human gate
 
-После аналитика:
+After the analyst:
 
-- Покажи пользователю ссылки на `brief.md` и `decomposition.md`.
-- Попроси проверить и утвердить или прислать правки.
-- Для продолжения: `/task-continue <slug>` или `/feature-continue <slug>`.
+- Show the user links to `brief.md` and `decomposition.md`.
+- Ask them to review and approve or send edits.
+- To continue: `/task-continue <slug>` or `/feature-continue <slug>`.
 
-## Если slug уже существует
+## If slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или continue.
-- Если задача в работе — спроси, продолжать или начать новый slug.
+- If `status.json` is `awaiting_approval` — offer review or continue.
+- If the task is in progress — ask whether to continue or start a new slug.

package/presets/cursor/go/commands/task-continue.md

@@ -3,25 +3,25 @@ name: task-continue
 description: Continue an agent-team task after a human gate, pause, or review changes request using pipeline.json and status.json.
 ---
 
-# Task continue — после human gate или паузы
+# Task continue — after human gate or pause
 
-Продолжение пайплайна из `pipeline.json`. Алиас по смыслу: `/feature-continue`.
+Resume the pipeline from `pipeline.json`. Semantic alias: `/feature-continue`.
 
-## Аргументы
+## Arguments
 
-`<slug>` — идентификатор задачи.
+`<slug>` — task identifier.
 
 ## Preconditions
 
-1. Прочитай `.cursor/team/tasks/<slug>/pipeline.json` и `status.json`.
-2. Продолжай если:
-   - `awaitingHumanGate: true` или `state: awaiting_approval`, **или**
-   - `state: changes_requested` (после review), **или**
-   - задача прервана и нужно возобновить с `pipelineIndex`.
+1. Read `.cursor/team/tasks/<slug>/pipeline.json` and `status.json`.
+2. Continue if:
+   - `awaitingHumanGate: true` or `state: awaiting_approval`, **or**
+   - `state: changes_requested` (after review), **or**
+   - the task was interrupted and must resume from `pipelineIndex`.
 
-## Алгоритм
+## Algorithm
 
-1. Запиши `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
+1. Write `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
 2. **Human gate resume** (`awaitingHumanGate` / `awaiting_approval`):
    1. **Do not** manually increment `pipelineIndex` or invent `currentAgent` first.
    2. Close the gate + activate the next attempt via the **installed** hook (single authority for ledger + status):
@@ -36,10 +36,10 @@ printf '%s\n' '{"status":"completed","action":"end_human_gate","activateNext":tr
 4. **Other resume**: restore `pipelineIndex` / `currentAgent` from status and invoke that agent.
 5. After the invoked agent completes, `chain-team-phases.sh` on `subagentStop` continues the chain when `autoChain: true`.
 
-## Артефакты для handoff
+## Artifacts for handoff
 
-| Agent | Прочитать |
-|-------|-----------|
+| Agent | Read |
+|-------|------|
 | feature-developer | brief.md, decomposition.md, validation-report.md (if retry), review.md (if retry), architecture.md |
 | build-verifier | git diff, decomposition.md |
 | code-reviewer | brief.md, validation-report.md, git diff |