@bonesofspring/ai-rules 0.2.13 → 0.2.15

package/presets/cursor/ios-swift/README.md

@@ -1,6 +1,6 @@
 # iOS Swift preset (Cursor)
 
-Правила и agent-team surface для iOS (Swift / SwiftUI / XCTest / XCUITest).
+Rules and agent-team surface for iOS (Swift / SwiftUI / XCTest / XCUITest).
 
 ## Install
 
@@ -8,15 +8,15 @@
 npx @bonesofspring/ai-rules init cursor --preset ios-swift
 ```
 
-Копирует:
+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 (iOS) |
 | `rules/**` | `.mdc` + README (alwaysApply ≤3) |
-| `agents/**` | **22** ролей (+ README rename map; includes on-demand `codebase-analyzer`) |
+| `agents/**` | **22** roles (+ README rename map; includes on-demand `codebase-analyzer`) |
 | `skills/**` | **8** skills (incl. `xcuitest-e2e`, `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/` |
@@ -27,7 +27,7 @@ npx @bonesofspring/ai-rules init cursor --preset ios-swift
 
 `ios-app-core`, `architecture-boundaries`, `code-quality-and-refactoring`.
 
-Requestable (не always-on): `post-change-build`, `xcode-tooling`, `agent-team-*`, `code-review-mr`, `feature-delivery-workflow`, `reference-features`.
+Requestable (not always-on): `post-change-build`, `xcode-tooling`, `agent-team-*`, `code-review-mr`, `feature-delivery-workflow`, `reference-features`.
 
 ## Preset taxonomy & contributing
 
@@ -38,8 +38,8 @@ Requestable (не always-on): `post-change-build`, `xcode-tooling`, `agent-team-
 
 ## Sync with Claude
 
-SoT = этот Cursor-пресет. После правок `.mdc` / agents / skills — обновить twin в `presets/claude/ios-swift/` **в том же PR**.
+SoT = this Cursor preset. After editing `.mdc` / agents / skills — update the twin in `presets/claude/ios-swift/` **in the same PR**.
 
-`BUGBOT.md` — **Cursor-only** (нет Claude twin); для Claude Code — skill `code-review` + `tooling-and-review/code-review.md`.
+`BUGBOT.md` is **Cursor-only** (no Claude twin); for Claude Code use skill `code-review` + `tooling-and-review/code-review.md`.
 
-См. `rules/README.md`, `AGENTS.md`.
+See `rules/README.md`, `AGENTS.md`.

package/presets/cursor/ios-swift/agents/README.md

@@ -1,6 +1,6 @@
 # `.cursor/agents` (preset ios-swift)
 
-Ролевые subagents для командного пайплайна Cursor (iOS / Swift / SwiftUI).
+Role subagents for the Cursor team pipeline (iOS / Swift / SwiftUI).
 
 ## next → ios-swift rename map
 
@@ -11,12 +11,12 @@
 | `playwright-test-generator` | **`xcuitest-test-generator`** |
 | `playwright-test-healer` | **`xcuitest-test-healer`** |
 
-When copying next pipeline templates: put Playwright stems in `skipped` with reason «iOS uses XCUITest» and schedule xcuitest trio instead.
+When copying next pipeline templates: put Playwright stems in `skipped` with reason "iOS uses XCUITest" and schedule xcuitest trio instead.
 
 ## Roster (22)
 
-| Agent | Production-код |
-|-------|----------------|
+| Agent | Production code |
+|-------|-----------------|
 | task-router, task-analyst, solution-architect, migration-specialist, api-contract-reviewer | no |
 | codebase-analyzer | no (explain-as-is only) |
 | feature-developer | yes |
@@ -28,7 +28,7 @@ When copying next pipeline templates: put Playwright stems in `skipped` with rea
 
 ## Frontmatter `readonly`
 
-Все agents — **`readonly: false`** (нужна запись в `.cursor/team/**`). Ограничения production — в теле промпта.
+All agents use **`readonly: false`** (team writes under `.cursor/team/**` are required). Production restrictions live in the prompt body.
 
 ## Model matrix (frontmatter `model`)
 
@@ -44,7 +44,7 @@ Optional `steps[].model`: `cheap` \| `standard` \| `strong` (router/orchestrator
 
 ## Pipeline routing
 
-**SoT:** intent table / profiles — **`task-router.md`**. Schema — ниже (same as next).
+**SoT:** intent table / profiles — **`task-router.md`**. Schema — below (same as next).
 
 ### pipeline.json (minimal)
 
@@ -67,4 +67,4 @@ Optional `steps[].model`: `cheap` \| `standard` \| `strong` (router/orchestrator
 
 `steps[].model` optional: `cheap` \| `standard` \| `strong`.
 
-Копируется в `.cursor/agents/` при `ai-rules init cursor --preset ios-swift`.
+Copied to `.cursor/agents/` on `ai-rules init cursor --preset ios-swift`.

package/presets/cursor/ios-swift/agents/build-verifier.md

@@ -35,7 +35,7 @@ When validating **ios-swift preset** changes (or `scope: preset-structure-valida
 3. **Forbidden handoff strings** in ios-swift `chain-team-phases.sh` (Cursor + Claude): `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`, and positive yarn lint recipes (`lint:js` / `lint:css` as commands to run — negation prose alone is not enough; prefer zero occurrences). See `preset-no-cross-stack-leakage.mdc`.
 4. **Required handoff stems:** `AGENT_HANDOFF` must include `xcuitest-test-planner` (or generator/healer) and `build-verifier` text must mention `xcodebuild` or `post-change-build` / `xcode-tooling`.
 5. **Roster:** 21 agent stems; no `playwright-test-*` files under ios-swift `agents/`.
-6. **Twin presence (hard):** Cursor rule change → Claude twin present **same PR** — **FAIL** if missing (next, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel).
+6. **Twin presence (hard):** Cursor rule change → Claude twin present **same PR** — **FAIL** if missing (next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel).
 7. **Mapping / README:** `claude/ios-swift/rules/README.md` mapping table present; core→stack mapping documented when `_shared` consumers exist.
 8. **shared-core consumers:** if `_shared/core/**` changed, every matching `<!-- shared-core: … -->` consumer in this PR must be updated (or intentional fork documented).
 9. **Session-start body budget:** sum of the **3** intended always-on / session-start rule bodies ≤ **140** lines (stretch ≤120); do **not** include `**/README.md` — record in report.
@@ -47,7 +47,7 @@ When validating **ios-swift preset** changes (or `scope: preset-structure-valida
 - **Thin aliases:** `agent-team-intake`, `technical-retro` may be &lt;15 body lines. Enforce ≥15 on **domain** rules (navigation, persistence, security, modules, networking, UI).
 - Embed vs lineage modes: `docs/PRESET-CONTRIBUTION.md`, `_shared/README.md`.
 
-12. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java|mcp-ts|php-hexagonal`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
+12. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|nuxt|svelte|ios-swift|go|java|mcp-ts|php-hexagonal|php-laravel`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
 13. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
 14. **No react-performance on ios/go/java:** skill directory / required handoff must be absent under ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel → **FAIL** (leakage). Prefer `check:preset-leakage`.
 15. **Rule eval (WARN):** `scripts/check-rule-eval.mjs` / `yarn check:rule-eval` should exist for maintainers; smoke optional. Hard fail only when the opt-in eval job runs — not part of default `check:preset-structure`.

package/presets/cursor/ios-swift/agents/feature-developer.md

@@ -16,7 +16,7 @@ You are a senior iOS developer (SwiftUI-first, SPM as in repo) with strict layer
 ## Rules
 
 - Scope: Features/Presentation/Domain/Data — not React/`app/src`.
-- Unit tests mandatory for mappers, use cases, non-trivial VM logic before handoff.
+- Unit tests must cover mappers, use cases, non-trivial VM logic before handoff.
 - Mark completed WPs in `decomposition.md`.
 - After Swift edits: **invoke** `post-change-build.mdc` (+ `xcode-tooling.mdc` for commands). If next step is `build-verifier`, scoped build/lint on changed targets is enough.
 

package/presets/cursor/ios-swift/agents/task-analyst.md

@@ -22,7 +22,7 @@ Ask only blocking questions (AC gaps, Feature scope, platforms, offline/auth, AP
 2. `decomposition.md` — ordered WPs with Depends on / Done when; mark unit/UI test WPs.
 3. Emit the analysis receipt; the runtime applies the configured analyst human gate.
 
-Do not invent architecture stacks (TCA, SwiftData, …) — frame «как в репо».
+Do not invent architecture stacks (TCA, SwiftData, …) — frame “as in the repo”.
 
 ## Design guidance (optional)
 

package/presets/cursor/ios-swift/agents/task-router.md

@@ -17,22 +17,22 @@ You are a task router for an **iOS Swift/SwiftUI** agent team. You **do not** im
 
 | intent | Signals | Default steps |
 |--------|---------|---------------|
-| `feature` | «добавь», «новая», «реализуй», Feature/UI/API | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or **xcuitest** trio |
-| `bugfix` | «баг», «fix», «не работает», «падает» | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer |
-| `ci-fix` | «CI», «Xcode Cloud», «красный PR», «failing check» | ci-investigator → feature-developer (skipIf resolved) → build-verifier → code-reviewer |
-| `migration` | «миграция», «upgrade», «обнови Xcode/SPM/iOS» | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer |
-| `perf-audit` | «производительность», «Instruments», «launch», «медленно» | performance-auditor |
-| `a11y` | «a11y», «VoiceOver», «Dynamic Type», «accessibility» | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
-| `review-only` | «ревью», «review MR», «проверь diff» | code-reviewer |
-| `test-only` | «покрой тестами» (unit+UI, no impl) | task-analyst → qa-tester |
-| `unit-only` | «unit», «юнит», «XCTest», «покрой mapper» | unit-test-planner → unit-test-generator, or unit-test-healer |
-| `e2e-only` | «e2e», «UI test», «XCUITest», «сценарии UI» | **xcuitest-test-planner** → **xcuitest-test-generator**, or **xcuitest-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`) |
-
-**Never schedule Playwright agents** (`playwright-test-*`). If a next template mentions them, put in `skipped` with reason «iOS uses XCUITest» and use xcuitest trio.
+| `feature` | “add”, “new”, “implement”, Feature/UI/API | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or **xcuitest** trio |
+| `bugfix` | “bug”, “fix”, “broken”, “crash” | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer |
+| `ci-fix` | “CI”, “Xcode Cloud”, “red PR”, “failing check” | ci-investigator → feature-developer (skipIf resolved) → build-verifier → code-reviewer |
+| `migration` | “migration”, “upgrade”, “update Xcode/SPM/iOS” | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer |
+| `perf-audit` | “performance”, “Instruments”, “launch”, “slow” | performance-auditor |
+| `a11y` | “a11y”, “VoiceOver”, “Dynamic Type”, “accessibility” | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
+| `review-only` | “review”, “review MR”, “check the diff” | code-reviewer |
+| `test-only` | “cover with tests” (unit+UI, no impl) | task-analyst → qa-tester |
+| `unit-only` | “unit”, “XCTest”, “cover mapper” | unit-test-planner → unit-test-generator, or unit-test-healer |
+| `e2e-only` | “e2e”, “UI test”, “XCUITest”, “UI scenarios” | **xcuitest-test-planner** → **xcuitest-test-generator**, or **xcuitest-test-healer** |
+| `docs-only` | “documentation”, “README”, “changelog” | task-analyst → tech-writer |
+| `refactor` | “refactor”, “no behavior change” | task-analyst → feature-developer → build-verifier → code-reviewer |
+| `spike` | “investigate”, “spike”, proof of concept | task-analyst → solution-architect |
+| `retro` | “retro”, “postmortem” | (orchestrator → `/technical-retro`) |
+
+**Never schedule Playwright agents** (`playwright-test-*`). If a next template mentions them, put in `skipped` with reason "iOS uses XCUITest" and use xcuitest trio.
 
 ## Pipeline profiles
 

package/presets/cursor/ios-swift/commands/README.md

@@ -1,51 +1,51 @@
 # Cursor commands (ios-swift preset)
 
-Slash-команды копируются в `.cursor/commands/` при `ai-rules init cursor --preset ios-swift`.
+Slash commands are copied to `.cursor/commands/` on `ai-rules init cursor --preset ios-swift`.
 
-## Команда агентов
+## Agent 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 point:** 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 Миграция на iOS Swift 15
+/task Migrate to iOS Swift 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 Сделай ревью изменений в Features/Orders
+/task Review changes in Features/Orders
 → reviewer only
 ```
 
-## Связанные файлы
+## Related files
 
-- Subagents: `../agents/` (22 ролей, включая `task-router.md`, `codebase-analyzer.md`, и `xcuitest-test-{planner,generator,healer}`)
-- Оркестратор: `../rules/agent-team-orchestrator.mdc`
+- Subagents: `../agents/` (22 roles, including `task-router.md`, `codebase-analyzer.md`, and `xcuitest-test-{planner,generator,healer}`)
+- Orchestrator: `../rules/agent-team-orchestrator.mdc`
 - Skills: `../skills/` (`feature-delivery`, `code-review`, `debug-investigation`, `ci-investigation`, `unit-testing`, `xcuitest-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/ios-swift/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 is 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. 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/ios-swift/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 chooses 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. Optional: 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 the 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/ios-swift/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`.
+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 |

package/presets/cursor/ios-swift/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 work. Parent agent = orchestrator (`agent-team-orchestrator.mdc`). Intake for work requests without `/task` — `agent-team-intake.mdc`.
 
-## Аргументы
+## Arguments
 
-Всё после `/task` — описание задачи на естественном языке.
+Everything after `/task` is a natural-language task description.
 
-Примеры:
+Examples:
 
-- `/task Добавить фильтр по дате в Order History`
-- `/task Order History падает при пустом списке — пофикси`
-- `/task CI упал на xcodebuild в PR`
-- `/task Миграция сетевого клиента / SPM зависимости`
-- `/task Проверь a11y формы логина`
-- `/task Покрой unit-тестами OrderMapper`
-- `/task Напиши changelog для релиза фильтров`
-- `/task Сделай ревью моих изменений в Features/Orders`
-- `/task Напиши XCUITest для сценария оплаты`
+- `/task Add a date filter to Order History`
+- `/task Order History crashes on an empty list — fix it`
+- `/task CI failed on xcodebuild in a PR`
+- `/task Migrate the network client / SPM dependency`
+- `/task Check a11y of the login form`
+- `/task Cover OrderMapper with unit tests`
+- `/task Write a changelog for the filters release`
+- `/task Review my changes in Features/Orders`
+- `/task Write an XCUITest for the payment flow`
 
-## Алгоритм
+## 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) — the 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` manually;
+   - invoke the subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
+6. **After each agent** — wait for hook handoff / reconciliation of the 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 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 taken
 
-- `awaitingHumanGate` / `state: awaiting_approval` → предложи ревью артефактов или `/task-continue <slug>`.
-- `in_progress` → спроси: продолжить или новый slug.
+- `awaitingHumanGate` / `state: awaiting_approval` → offer artifact review or `/task-continue <slug>`.
+- `in_progress` → ask: continue or new slug.
 
 ## Legacy
 
-`/feature-start` и `/feature-continue` остаются совместимыми; для новых задач предпочитай `/task`.
+`/feature-start` and `/feature-continue` remain compatible; prefer `/task` for new work.
 
 ## Metrics