@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/presets/cursor/svelte/README.md

@@ -1,6 +1,6 @@
 # SvelteKit preset (Cursor)
 
-Правила и agent-team surface для SvelteKit / Svelte 5 / TypeScript.
+Rules and agent-team surface for SvelteKit / Svelte 5 / TypeScript.
 
 ## Install
 
@@ -8,15 +8,15 @@
 npx @bonesofspring/ai-rules init cursor --preset svelte
 ```
 
-Копирует:
+Copies:
 
-| Path | Содержание |
-|------|------------|
+| Path | Contents |
+|------|----------|
 | `REPO_AGENTS.md` | → repo-root `AGENTS.md` (cross-tool) |
 | `AGENTS.md` | → `.cursor/AGENTS.md` quick-start |
 | `BUGBOT.md` | Cursor Bugbot review priorities |
 | `rules/**` | `.mdc` + README (alwaysApply ≤3); golden rules with Incorrect/Correct + `impact:` |
-| `agents/**` | **22** ролей (+ README; includes on-demand `codebase-analyzer`) |
+| `agents/**` | **22** roles (+ README; includes on-demand `codebase-analyzer`) |
 | `skills/**` | 9 skills (incl. `playwright-e2e`, `write-adr`, `svelte-performance`) |
 | `commands/**` | task, task-continue, feature-start/continue, technical-retro |
 | `hooks.json` + `hooks/**` | guard-shell + chain-team-phases; optional `hooks/examples/` cookbook |
@@ -27,7 +27,7 @@ npx @bonesofspring/ai-rules init cursor --preset svelte
 
 `svelte-app-core`, `package-manager`, `code-quality-and-refactoring`.
 
-Requestable (не always-on): `post-change-lint`, `agent-team-*`, `code-review-mr`, `feature-delivery-workflow`, `reference-features`, domain globs.
+Requestable (not always-on): `post-change-lint`, `agent-team-*`, `code-review-mr`, `feature-delivery-workflow`, `reference-features`, domain globs.
 
 ## Preset taxonomy & contributing
 
@@ -38,10 +38,10 @@ Requestable (не always-on): `post-change-lint`, `agent-team-*`, `code-review-m
 
 ## Sync with Claude
 
-SoT = этот Cursor-пресет. После правок `.mdc` / agents / skills — обновить twin в `presets/claude/svelte/` **в том же PR**.
+SoT = this Cursor preset. After edits to `.mdc` / agents / skills — update the twin in `presets/claude/svelte/` **in the same PR**.
 
-`BUGBOT.md` — **Cursor-only** (нет Claude twin); для Claude Code — skill `code-review` + `tooling-and-review/code-review.md`.
+`BUGBOT.md` — **Cursor-only** (no Claude twin); for Claude Code — skill `code-review` + `tooling-and-review/code-review.md`.
 
 Claude→Cursor map: `presets/claude/svelte/rules/README.md`.
 
-См. также `AGENTS.md`.
+See also `AGENTS.md`.

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

@@ -1,45 +1,45 @@
 # `.cursor/agents` (preset svelte)
 
-Ролевые subagents для командного пайплайна Cursor.
+Role subagents for the Cursor team pipeline.
 
 ## Planning and routing
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | Router | `task-router.md` | no |
-| Аналитик | `task-analyst.md` | no |
-| Архитектор | `solution-architect.md` | no |
+| Analyst | `task-analyst.md` | no |
+| Architect | `solution-architect.md` | no |
 | Migration planner | `migration-specialist.md` | no |
 | API contract reviewer | `api-contract-reviewer.md` | no |
 
 ## Analysis (on-demand)
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | Codebase analyzer | `codebase-analyzer.md` | no (explain-as-is only) |
 
 ## Implementation and CI
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | Debugger | `debugger.md` | minimal fix only |
 | CI investigator | `ci-investigator.md` | minimal CI fix only |
 | Build verifier | `build-verifier.md` | no |
-| Разработчик | `feature-developer.md` | yes |
+| Developer | `feature-developer.md` | yes |
 
 ## Review specialists
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
-| Ревьюер | `code-reviewer.md` | no |
+| Agent | File | Production code |
+|-------|------|-----------------|
+| Reviewer | `code-reviewer.md` | no |
 | A11y reviewer | `accessibility-reviewer.md` | no |
 | Security reviewer | `security-reviewer.md` | no |
 | Performance auditor | `performance-auditor.md` | no |
 
 ## Testing
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | QA | `qa-tester.md` | tests only |
 | Unit planner | `unit-test-planner.md` | no |
 | Unit generator | `unit-test-generator.md` | tests only |
@@ -50,21 +50,21 @@
 
 ## Documentation
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | Tech writer | `tech-writer.md` | docs only |
 
-Копируется в `.cursor/agents/` при `ai-rules init cursor --preset svelte`.
+Copied to `.cursor/agents/` on `ai-rules init cursor --preset svelte`.
 
 ## Frontmatter `readonly`
 
-Все agents пайплайна — **`readonly: false`**. Им нужна запись в `.cursor/team/**` (`pipeline.json`, `brief.md`, `review.md`, `status.json`, …).
+All pipeline agents are **`readonly: false`**. They need write access under `.cursor/team/**` (`pipeline.json`, `brief.md`, `review.md`, `status.json`, …).
 
-Ограничение «не трогать production / `app/**`» задаётся **в теле промпта**, не флагом `readonly`. В Cursor `readonly: true` блокирует *любые* file edits (включая team) — для team-агентов это ломает пайплайн.
+The “do not touch production / `app/**`” limit is set **in the prompt body**, not via the `readonly` flag. In Cursor `readonly: true` blocks *any* file edits (including team) — that breaks the pipeline for team agents.
 
 ## Model matrix (frontmatter `model`)
 
-SoT по умолчанию — YAML `model` в каждом agent-файле. Опциональный `steps[].model` (`cheap` \| `standard` \| `strong`) переопределяет тир на шаге пайплайна (см. `task-router.md`, `agent-team-orchestrator.mdc`).
+Default SoT — YAML `model` in each agent file. Optional `steps[].model` (`cheap` \| `standard` \| `strong`) overrides the tier for a pipeline step (see `task-router.md`, `agent-team-orchestrator.mdc`).
 
 | Tier | Default frontmatter | Agents |
 |------|---------------------|--------|
@@ -74,20 +74,20 @@ SoT по умолчанию — YAML `model` в каждом agent-файле.
 
 **Notes**
 
-- `inherit` = модель parent-чата (обычно сильнее `fast`).
+- `inherit` = parent-chat model (usually stronger than `fast`).
 - Strong pin uses Cursor bracket options (`[effort=high]`). If the ID is blocked by plan/admin, Cursor falls back to a compatible model.
 - Alternate strong pin when Opus unavailable: `composer-2.5[fast=false]` (edit frontmatter locally).
 - Never put `strong` on `build-verifier` / `tech-writer` / `task-router`.
 
-## Оркестрация
+## Orchestration
 
-| Command | Назначение |
-|---------|------------|
-| `/task <desc>` | Router → dynamic pipeline → первый agent |
-| `/task-continue <slug>` | После human gate |
-| `/feature-start`, `/feature-continue` | Legacy (совместимость) |
+| Command | Purpose |
+|---------|---------|
+| `/task <desc>` | Router → dynamic pipeline → first agent |
+| `/task-continue <slug>` | After a human gate |
+| `/feature-start`, `/feature-continue` | Legacy (compatibility) |
 
-Правило: `agent-team-orchestrator.mdc`. План: `pipeline.json` в `.cursor/team/tasks/<slug>/`.
+Rule: `agent-team-orchestrator.mdc`. Plan: `pipeline.json` under `.cursor/team/tasks/<slug>/`.
 
 ## Pipeline routing
 

package/presets/cursor/svelte/agents/feature-developer.md

@@ -17,7 +17,7 @@ You are a senior frontend developer working in a SvelteKit monorepo with strict
 ## Task execution rules
 
 - Do **not** start blocked tasks or tasks with incomplete dependencies.
-- **Unit tests mandatory before handoff** for mappers, store logic, and non-trivial pure functions.
+- **Unit tests must run before handoff** for mappers, store logic, and non-trivial pure functions.
 - Mark completed tasks in `decomposition.md`.
 - Validation: **`post-change-lint.mdc`**. If pipeline next step is **`build-verifier`**, scoped lint/check on **changed files** is enough; full project lint is build-verifier's job.
 

package/presets/cursor/svelte/agents/task-analyst.md

@@ -9,7 +9,7 @@ You are a senior business/technical analyst for a SvelteKit frontend team.
 
 Your job is to reach **Definition of Ready (DoR)** before any implementation starts. You may write only `.cursor/team/**` artifacts. You do **not** write production code or modify application source files.
 
-## Clarification cycle (mandatory)
+## Clarification cycle (must)
 
 1. Rephrase the task in your own words (goal, user value, boundaries).
 2. Ask **1–3 questions per iteration** — never more than 3 at once.

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

@@ -17,20 +17,20 @@ You are a task router for a SvelteKit frontend agent team. You **do not** implem
 
 | intent | Signals in prompt | Default steps |
 |--------|-------------------|---------------|
-| `feature` | «добавь», «новая», «реализуй», «сделай», new UI/API/store | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or playwright trio |
-| `bugfix` | «баг», «fix», «не работает», «падает», «ошибка», regression | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer → qa-tester (regression) |
-| `ci-fix` | «CI», «упал пайплайн», «красный PR», «failing check», «lint в CI» | ci-investigator → feature-developer (skipIf ci-investigator.resolved) → build-verifier → code-reviewer |
-| `migration` | «миграция», «upgrade», «обнови Next», «переход на», major version | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer → qa-tester (regression) |
-| `perf-audit` | «производительность», «perf», «bundle», «LCP», «медленно», «waterfall» | performance-auditor |
-| `a11y` | «a11y», «доступность», «accessibility», «WCAG», «screen reader», «клавиатура» | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
-| `review-only` | «ревью», «review MR», «проверь diff», «code review» | code-reviewer |
-| `test-only` | «покрой тестами», «напиши тесты» (mixed unit+e2e, no impl) | task-analyst → qa-tester |
-| `unit-only` | «unit», «юнит», «mapper tests», «покрой маппер», «почини unit» | unit-test-planner → unit-test-generator, or unit-test-healer |
-| `e2e-only` | «e2e», «playwright», «browser test», «сценарии e2e», «почини e2e» | playwright-test-planner → playwright-test-generator, or playwright-test-healer |
-| `docs-only` | «документация», «README», «changelog», «ADR», «migration guide» | task-analyst → tech-writer |
-| `refactor` | «рефакторинг», «без изменения поведения», «почисти» | task-analyst → feature-developer → build-verifier → code-reviewer |
-| `spike` | «исследуй», «оцени», «можно ли», «spike», proof of concept | task-analyst → solution-architect |
-| `retro` | «ретро», «разбор», «postmortem» | (no pipeline — orchestrator runs `/technical-retro`) |
+| `feature` | “add”, “new”, “implement”, “build”, new UI/API/store | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or playwright trio |
+| `bugfix` | “bug”, “fix”, “broken”, “crash”, “error”, regression | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer → qa-tester (regression) |
+| `ci-fix` | “CI”, “pipeline failed”, “red PR”, “failing check”, “lint in CI” | ci-investigator → feature-developer (skipIf ci-investigator.resolved) → build-verifier → code-reviewer |
+| `migration` | “migration”, “upgrade”, “update SvelteKit”, “move to”, major version | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer → qa-tester (regression) |
+| `perf-audit` | “performance”, “perf”, “bundle”, “LCP”, “slow”, “waterfall” | performance-auditor |
+| `a11y` | “a11y”, “accessibility”, “WCAG”, “screen reader”, “keyboard” | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
+| `review-only` | “review”, “review MR”, “check diff”, “code review” | code-reviewer |
+| `test-only` | “cover with tests”, “write tests” (mixed unit+e2e, no impl) | task-analyst → qa-tester |
+| `unit-only` | “unit”, “mapper tests”, “cover the mapper”, “fix unit” | unit-test-planner → unit-test-generator, or unit-test-healer |
+| `e2e-only` | “e2e”, “playwright”, “browser test”, “e2e scenarios”, “fix e2e” | playwright-test-planner → playwright-test-generator, or playwright-test-healer |
+| `docs-only` | “documentation”, “README”, “changelog”, “ADR”, “migration guide” | task-analyst → tech-writer |
+| `refactor` | “refactor”, “no behavior change”, “clean up” | task-analyst → feature-developer → build-verifier → code-reviewer |
+| `spike` | “investigate”, “evaluate”, “is it possible”, “spike”, proof of concept | task-analyst → solution-architect |
+| `retro` | “retro”, “postmortem”, “retrospective” | (no pipeline — orchestrator runs `/technical-retro`) |
 
 ## Pipeline profiles
 
@@ -40,9 +40,9 @@ Set optional top-level `"profile": "full" | "standard" | "light"` in `pipeline.j
 |---------|------|------------------------|
 | `full` | Multi-layer, new public API, e2e coverage needed, incomplete AC | analyst → [architect] → developer → build-verifier → reviewer → qa-tester |
 | `standard` | Single layer, default work | analyst → developer → build-verifier → reviewer |
-| `light` | Trivial: one file/layer, explicit AC, «просто поправь», «typo», user «без pipeline» | developer → build-verifier |
+| `light` | Trivial: one file/layer, explicit AC, “just fix it”, “typo”, user “no pipeline” | developer → build-verifier |
 
-**Light signals:** один файл, один слой, явный AC в промпте, нет архитектурного риска. **Never skip `build-verifier`** after developer when `app/**` changed. **Skip `code-reviewer`** in light only for non-prod preset/docs tasks — for `pages/components/stores` changes prefer standard.
+**Light signals:** one file, one layer, explicit AC in the prompt, no architecture risk. **Never skip `build-verifier`** after developer when app sources changed. **Skip `code-reviewer`** in light only for non-prod preset/docs tasks — for `routes/components/stores` changes prefer standard.
 
 **Light by intent:**
 

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

@@ -1,51 +1,51 @@
-# Cursor commands (next preset)
+# Cursor commands (svelte preset)
 
-Slash-команды копируются в `.cursor/commands/` при `ai-rules init cursor --preset svelte`.
+Slash commands are copied to `.cursor/commands/` on `ai-rules init cursor --preset svelte`.
 
-## Команда агентов
+## Agent team commands
 
-| Command | Назначение |
-|---------|------------|
-| **`/task <описание>`** | **Главная точка входа:** router → pipeline.json → нужные роли по порядку |
-| `/task-continue <slug>` | После human gate или паузы |
-| `/feature-start <описание>` | Legacy: только analyst (без router) |
-| `/feature-continue <slug>` | Alias task-continue |
-| `/technical-retro [slug]` | Ретро; с slug — блок «Работа агентов» |
+| Command | Purpose |
+|---------|---------|
+| **`/task <description>`** | **Main entry:** router → pipeline.json → roles in order |
+| `/task-continue <slug>` | After a human gate or pause |
+| `/feature-start <description>` | Legacy: analyst only (no router) |
+| `/feature-continue <slug>` | Alias of task-continue |
+| `/technical-retro [slug]` | Retro; with slug — “Agent work” block |
 
-## Примеры `/task`
+## `/task` examples
 
 ```
-/task Добавить фильтр по дате в Order History
+/task Add a date filter to Order History
 → analyst → developer → reviewer → QA
 
-/task Order History падает при пустом списке
+/task Order History crashes on an empty list
 → debugger → developer → reviewer → QA (regression)
 
-/task CI упал на lint в PR #142
+/task CI failed on lint in PR #142
 → ci-investigator → developer → reviewer
 
-/task Миграция на SvelteKit 15
+/task Migrate to SvelteKit 15
 → analyst → migration-specialist → developer → reviewer → QA
 
-/task Проверь доступность модалки оплаты
+/task Check accessibility of the payment modal
 → analyst → developer → a11y-reviewer → code-reviewer
 
-/task Покрой unit-тестами mapper orders
+/task Cover the orders mapper with unit tests
 → unit-planner → unit-generator
 
-/task Напиши README для новой фичи фильтров
+/task Write a README for the new filters feature
 → analyst → tech-writer
 
-/task Сделай ревью изменений в store/orders
+/task Review changes in store/orders
 → reviewer only
 ```
 
-## Связанные файлы
+## Related files
 
-- Subagents: `../agents/` (**22** ролей, включая `task-router.md`, `codebase-analyzer.md`)
-- Оркестратор: `../rules/agent-team-orchestrator.mdc`
+- Subagents: `../agents/` (**22** roles, including `task-router.md`, `codebase-analyzer.md`)
+- Orchestrator: `../rules/agent-team-orchestrator.mdc`
 - Skills: `../skills/` (`feature-delivery`, `code-review`, `debug-investigation`, `ci-investigation`, `unit-testing`, `playwright-e2e`, `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/svelte/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`.
+> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
 
-Продолжение после human gate. Полная логика — в **`task-continue.md`**.
+Continue after a human gate. Full logic — in **`task-continue.md`**.
 
-## Кратко
+## Short form
 
-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. Invoke 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/svelte/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 выберет роли и порядок автоматически.
+> **Prefer:** `/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 the 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: a 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 the 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 the slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или continue.
-- Если задача в работе — спроси, продолжать или начать новый slug.
+- If `status.json` is `awaiting_approval` — suggest review or continue.
+- If the task is in progress — ask whether to continue or start a new slug.

package/presets/cursor/svelte/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 a human gate or pause
 
-Продолжение пайплайна из `pipeline.json`. Алиас по смыслу: `/feature-continue`.
+Continue 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 needs 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 |

package/presets/cursor/svelte/commands/task.md

@@ -3,53 +3,53 @@ name: task
 description: Route a natural-language task through the agent-team pipeline: task-router, pipeline.json, and the first planned specialist.
 ---
 
-# Task — единая точка входа (router + pipeline)
+# Task — single entry point (router + pipeline)
 
-Главная команда для постановки задачи. Родительский агент = оркестратор (`agent-team-orchestrator.mdc`). Intake для work-запросов без `/task` — `agent-team-intake.mdc`.
+Main command for filing a task. Parent agent = orchestrator (`agent-team-orchestrator.mdc`). Intake for work requests without `/task` — `agent-team-intake.mdc`.
 
-## Аргументы
+## Arguments
 
-Всё после `/task` — описание задачи на естественном языке.
+Everything after `/task` is the natural-language task description.
 
-Примеры:
+Examples:
 
-- `/task Добавить фильтр по дате в Order History`
-- `/task Order History падает при пустом списке — пофикси`
-- `/task CI упал на typecheck в PR`
-- `/task Миграция HTTP-клиента на fetch`
-- `/task Проверь a11y формы логина`
-- `/task Покрой unit-тестами mapper payments`
-- `/task Напиши changelog для релиза фильтров`
-- `/task Сделай ревью моих изменений в store/orders`
-- `/task Напиши e2e для сценария оплаты`
+- `/task Add a date filter to Order History`
+- `/task Order History crashes on an empty list — fix it`
+- `/task CI failed on typecheck in the PR`
+- `/task Migrate the HTTP client to fetch`
+- `/task Check a11y of the login form`
+- `/task Cover the payments mapper with unit tests`
+- `/task Write a changelog for the filters release`
+- `/task Review my changes in store/orders`
+- `/task Write e2e for the payment scenario`
 
-## Алгоритм
+## Algorithm
 
-1. **Slug** — kebab-case из описания (≤48 символов). Создай `.cursor/team/tasks/<slug>/` через **Write** (например placeholder `pipeline.json` или пустой marker) — runtime/hook владеет `status.json` — **не** через Shell `mkdir` (песочница → `Operation not permitted`).
-2. **Router** — вызови subagent **task-router** с описанием задачи и путём к slug.
-3. **План** — покажи пользователю таблицу из `pipeline.json`: intent, steps, skipped, humanGates.
-4. **Intent retro** — если `intent === "retro"`, выполни `/technical-retro` и **остановись**.
-5. **Старт** — после router:
-   - подтверди `pipeline.json` и `active-task.json`;
-   - **не** пиши lifecycle-поля `status.json` / `metrics.json` сам — их владеет orchestration runtime/hook (см. **agent-artifact-contracts**). Если `status.json` отсутствует, допустим только минимальный bootstrap (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **не** увеличивай `pipelineIndex` вручную;
-   - вызови subagent для `pipeline.steps[0].agent` (slug, пути к артефактам, scope).
-6. **После каждого агента** — дождись hook handoff / reconciliation terminal receipt → `status.state`; не запускай следующий шаг, пока `status.json` не отражает handoff (или пока нет `followup_message` от hook).
-7. **Human gate** — если после текущего шага есть gate в `humanGates` (`after:<agent>`), после завершения агента **остановись** и попроси `/task-continue <slug>` (или `/feature-continue <slug>`).
+1. **Slug** — kebab-case from the description (≤48 characters). Create `.cursor/team/tasks/<slug>/` via **Write** (e.g. placeholder `pipeline.json` or empty marker) — runtime/hook owns `status.json` — **not** via Shell `mkdir` (sandbox → `Operation not permitted`).
+2. **Router** — invoke subagent **task-router** with the task description and slug path.
+3. **Plan** — show the user the table from `pipeline.json`: intent, steps, skipped, humanGates.
+4. **Intent retro** — if `intent === "retro"`, run `/technical-retro` and **stop**.
+5. **Start** — after the router:
+   - confirm `pipeline.json` and `active-task.json`;
+   - **do not** write `status.json` / `metrics.json` lifecycle fields yourself — the orchestration runtime/hook owns them (see **agent-artifact-contracts**). If `status.json` is missing, only a minimal bootstrap is allowed (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **do not** increment `pipelineIndex` by hand;
+   - invoke the subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
+6. **After each agent** — wait for hook handoff / reconciliation terminal receipt → `status.state`; do not start the next step until `status.json` reflects the handoff (or until there is a hook `followup_message`).
+7. **Human gate** — if after the current step there is a gate in `humanGates` (`after:<agent>`), after the agent finishes **stop** and ask for `/task-continue <slug>` (or `/feature-continue <slug>`).
 
-## Не делать
+## Do not
 
-- Не вызывать developer до router и (если в pipeline) analyst/architect.
-- Не hardcode порядок ролей — только `pipeline.json`.
-- Не пропускать human gate без явного continue.
+- Do not invoke the developer before the router and (if in the pipeline) analyst/architect.
+- Do not hardcode role order — only `pipeline.json`.
+- Do not skip a human gate without an explicit continue.
 
-## Если slug занят
+## If the slug is busy
 
-- `awaitingHumanGate` / `state: awaiting_approval` → предложи ревью артефактов или `/task-continue <slug>`.
-- `in_progress` → спроси: продолжить или новый slug.
+- `awaitingHumanGate` / `state: awaiting_approval` → suggest reviewing artifacts or `/task-continue <slug>`.
+- `in_progress` → ask: continue or a new slug.
 
 ## Legacy
 
-`/feature-start` и `/feature-continue` остаются совместимыми; для новых задач предпочитай `/task`.
+`/feature-start` and `/feature-continue` remain compatible; prefer `/task` for new work.
 
 ## Metrics