@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/presets/claude/nuxt/rules/tooling-and-review/preset-token-budget.md

@@ -6,21 +6,20 @@ paths:
 
 <!-- shared-core: meta/preset-token-budget.md -->
 
-
 # Preset token budget
 
-Инварианты загрузки правил в **установленном** пресете (consumer app).
+Invariants for rule loading in an **installed** preset (consumer app).
 
 ## Hard caps
 
 | Platform | Always-on | Cap |
 |----------|-----------|-----|
 | Cursor | `alwaysApply: true` | **≤ 3** |
-| Claude | rules **without** `paths:` | **ровно 3** |
+| Claude | rules **without** `paths:` | **exactly 3** |
 
 **Claude Option A (README exclusion):** when counting Claude rules without `paths:` / session-start, **exclude `**/README.md`** (topic indexes are not session-start rules). The intended session-start trio remains **exactly 3**; body budget sums **only those 3** rules.
 
-Session-start body budget (где задокументировано): ≤140 строк суммарно (stretch ≤120).
+Session-start body budget (where documented): ≤140 lines total (stretch ≤120).
 
 ## Meta / author rules
 

package/presets/claude/nuxt/rules/tooling-and-review/preset-twin-sync.md

@@ -2,8 +2,8 @@
 description: Preset authoring: Cursor SoT → Claude twin same PR. Use when editing preset rules.
 paths: packages/ai-rules/presets/**
 ---
-<!-- shared-core: meta/preset-twin-sync.md -->
 
+<!-- shared-core: meta/preset-twin-sync.md -->
 
 # Preset twin sync
 

package/presets/claude/nuxt/rules/tooling-and-review/technical-retro.md

@@ -1,15 +1,16 @@
 ---
-description: Роль агента для проведения технического ретроспективы (retro) команды / спринта. On-demand — предпочтительнее slash-команда /technical-retro.
+description: Agent role for running a technical retrospective (retro) for a team / sprint. On-demand — prefer the /technical-retro slash command.
 paths: .claude/team/**
 ---
+
 <!-- shared-core: review/technical-retro.md -->
 
-# Техническое ретро — rule alias
+# Technical retro — rule alias
 
-Полный сценарий (включая блок **«Работа агентов»** для slug из team tasks) — в slash-команде:
+Full scenario (including the **“Agent work”** block for a slug from team tasks) lives in the slash command:
 
 **`commands/technical-retro.md`** → `/technical-retro`
 
 When a task has `metrics.json`, use the local aggregation script and state the cohort, sample size, incomplete artifacts, attribution confidence, active attempt duration, and human-gate wait separately. Do not score malformed artifacts or gate wait as agent work.
 
-Используй rule только если command недоступен. Не дублируй содержимое command в ответе — следуй command-файлу и skill `technical-retro`.
+Use this rule only if the command is unavailable. Do not duplicate the command contents in the response — follow the command file and skill `technical-retro`.

package/presets/claude/nuxt/rules/ui-and-accessibility/README.md

@@ -1,12 +1,12 @@
 # UI and accessibility
 
-Компоненты, стили, пропсы.
+Components, styles, props.
 
-| Файл | Содержание | Загрузка |
-|------|------------|----------|
-| `no-v-bind-spread.md` | Явные пропсы, без `v-bind="obj"` | `paths: **/*.{vue,tsx,jsx}` |
-| `css-property-order.md` | Порядок CSS (Stylelint idiomatic-order) | `paths: **/*.{css,scss,vue}` |
-| `vue-ui.md` | Структура SFC, стили, composables | `paths: components|pages|layouts/**/*.{vue,ts}` |
-| `vue-a11y-coding.md` | A11y при написании UI | `paths: components|pages|layouts/**/*.{vue,ts}` |
+| File | Contents | Loading |
+|------|----------|---------|
+| `no-v-bind-spread.md` | Explicit props, no `v-bind="obj"` | `paths: **/*.{vue,tsx,jsx}` |
+| `css-property-order.md` | CSS property order (Stylelint idiomatic-order) | `paths: **/*.{css,scss,vue}` |
+| `vue-ui.md` | SFC structure, styles, composables | `paths: components|pages|layouts/**/*.{vue,ts}` |
+| `vue-a11y-coding.md` | A11y while writing UI | `paths: components|pages|layouts/**/*.{vue,ts}` |
 
 Deprecated stub `component-styles.md` **removed** — styles colocation lives in `vue-ui.md`.

package/presets/claude/nuxt/rules/ui-and-accessibility/vue-ui.md

@@ -5,15 +5,16 @@ paths:
   - "pages/**/*.{vue,ts}"
   - "layouts/**/*.{vue,ts}"
 ---
+
 # Vue UI (Nuxt)
 
-- Предпочитать **SFC** с `<script setup lang="ts">` (`script-setup-conventions`).
-- Явные `defineProps` / `defineEmits` (typed); без массового `v-bind="object"` (`no-v-bind-spread`).
-- Стили: scoped / CSS modules / design tokens — как у соседей; порядок свойств — `css-property-order-stylelint`.
-- Данные: читать Pinia / composables; **не** вызывать HTTP из SFC — только через `~/api` / store actions.
-- Навигация: `<NuxtLink>`, `navigateTo`, `useRouter` / `useRoute` — не `next/link` / `next/navigation`.
+- Prefer **SFC** with `<script setup lang="ts">` (`script-setup-conventions`).
+- Explicit `defineProps` / `defineEmits` (typed); no bulk `v-bind="object"` (`no-v-bind-spread`).
+- Styles: scoped / CSS modules / design tokens — as neighbors; property order — `css-property-order-stylelint`.
+- Data: read Pinia / composables; **do not** call HTTP from SFC — only via `~/api` / store actions.
+- Navigation: `<NuxtLink>`, `navigateTo`, `useRouter` / `useRoute` — not `next/link` / `next/navigation`.
 - A11y: `vue-a11y-coding`.
-- Границы UI: `architecture-boundaries-ui` — no DTO in templates; map in `api/**`.
+- UI boundaries: `architecture-boundaries-ui` — no DTO in templates; map in `api/**`.
 
 ## Incorrect
 

package/presets/claude/nuxt/skills/README.md

@@ -1,9 +1,9 @@
 # `.claude/skills` (preset nuxt)
 
-[Skills](https://code.claude.com/docs/en/skills) в Claude Code — сценарии, которые подгружаются по необходимости, а не в каждой сессии целиком. Они синхронизированы по смыслу с `.cursor/skills` из Cursor-пресета.
+[Skills](https://code.claude.com/docs/en/skills) in Claude Code are scenarios loaded on demand, not wholesale every session. They are semantically synced with `.cursor/skills` from the Cursor preset.
 
-| Skill | Когда использовать |
-|-------|--------------------|
+| Skill | When to use |
+|-------|-------------|
 | `feature-delivery` | End-to-end feature work across types, API, store, UI, tests |
 | `code-review` | MR/diff review using project architecture and test standards |
 | `debug-investigation` | Reproducing and fixing bugs with root-cause evidence |
@@ -14,4 +14,4 @@
 | `write-adr` | Author an Architecture Decision Record (context / decision / consequences) |
 | `vue-performance` | Implementer checklist: bundle, SSR/payload/client, memo, waterfalls, CWV (not a perf audit agent) |
 
-Папка копируется в `.claude/skills/` при `ai-rules init claude --preset nuxt`, если существует.
+The folder is copied to `.claude/skills/` on `ai-rules init claude --preset nuxt` when it exists.

package/presets/claude/nuxt/skills/feature-delivery/SKILL.md

@@ -8,7 +8,7 @@ description: Delivers Nuxt 3 frontend features end-to-end across domain types, A
 1. Read task brief, acceptance criteria, and decomposition if present.
 2. Read **`rules/architecture/feature-delivery-workflow.md`** and **`rules/architecture/reference-features.md`** — follow layer order and mirror closest reference feature.
 3. Add or update focused tests for changed behavior.
-4. Validation from repository root: **invoke** **`rules/tooling-and-review/post-change-lint.md`** after code edits (requestable, not session-start — but mandatory when code changed). Pipeline: scoped lint OK if next step is `build-verifier`.
+4. Validation from repository root: **invoke** **`rules/tooling-and-review/post-change-lint.md`** after code edits (requestable, not session-start — but **must** when code changed). Pipeline: scoped lint OK if next step is `build-verifier`.
 
 ## Scope discipline
 

package/presets/claude/nuxt/team/README.md

@@ -1,6 +1,6 @@
 # Agent team artifacts
 
-Каталог артефактов пайплайна «команда агентов» Claude.
+Artifact directory for the Claude Code “agent team” pipeline.
 
 ## Layout
 
@@ -97,16 +97,20 @@ Prefer **`executing`** for pipeline mode. Legacy: `analysis`, `development`, `re
 ## Workflow entry
 
 ```bash
-/task <описание задачи>
+/task <task description>
 /task-continue <slug>
 /technical-retro <slug>
 ```
 
 Legacy: `/feature-start`, `/feature-continue`.
 
+## Creating task dirs
+
+Bootstrap `<slug>/` by **writing** `pipeline.json` (Write tool). Runtime/hook owns `status.json` lifecycle; parent may only create a minimal bootstrap if missing. Do **not** use Shell `mkdir -p` — Cursor’s default sandbox returns `Operation not permitted` (especially for repos on macOS Desktop/Documents).
+
 ## Git
 
-Commit task artifacts if you want them to survive `ai-rules clean claude`. Or copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.
+Commit task artifacts if you want them to survive `ai-rules clean cursor`. Or copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.
 
 ## Artifact manifest and receipts
 
@@ -131,6 +135,6 @@ After a human gate, `/task-continue` closes wait via the installed hook (do not
 printf '%s\n' '{"status":"completed","action":"end_human_gate","activateNext":true}' | bash .claude/hooks/chain-team-phases.sh
 ```
 
-That appends `human_gate_ended` before the next `attempt_started`. Cursor twin uses the same payload against `.cursor/hooks/chain-team-phases.sh`. Other installable stacks ship the same ledger contract in their `team/README.md`.
+That appends `human_gate_ended` before the next `attempt_started`. Claude twins use the same payload against `.claude/hooks/chain-team-phases.sh`. Other installable stacks ship the same ledger contract in their `team/README.md`.
 
 Aggregate with `node packages/ai-rules/scripts/aggregate-agent-task-metrics.mjs --team-root .claude/team`. It reports role/agent count, completed count, total/average duration, distinct completed run IDs, separate human-gate wait, and incomplete artifacts. For retros, see `/technical-retro` → **Metrics evidence**.

package/presets/claude/php-hexagonal/MCP.md

@@ -1,15 +1,15 @@
 # MCP (preset `php-hexagonal`, Claude)
 
-Копируется в project `.mcp.json` при `ai-rules init claude --preset php-hexagonal`.
+Copied to the project `.mcp.json` on `ai-rules init claude --preset php-hexagonal`.
 
 ## Servers
 
-| Name | Package | Зачем |
-|------|---------|--------|
-| `context7` | `@upstash/context7-mcp` | Актуальная документация PHP / Composer / популярных библиотек |
+| Name | Package | Purpose |
+|------|---------|---------|
+| `context7` | `@upstash/context7-mcp` | Up-to-date PHP / Composer / popular library docs |
 
-Figma и browser e2e MCP (Playwright / Chrome DevTools) **не** входят в php-hexagonal-пресет (backend-only).
+Figma and browser e2e MCP (Playwright / Chrome DevTools) are **not** part of the php-hexagonal preset (backend-only).
 
-Секреты в файл не кладём. Опционально: `CONTEXT7_API_KEY` в окружении.
+Do not put secrets in the file. Optional: `CONTEXT7_API_KEY` in the environment.
 
-После init: включить MCP серверы в Claude Code. `init` перезаписывает одноимённый `mcp.json`.
+After init: enable MCP servers in Claude Code. `init` overwrites the same-named `mcp.json`.

package/presets/claude/php-hexagonal/agents/README.md

@@ -1,11 +1,11 @@
 # `.claude/agents` (preset php-hexagonal)
 
-Ролевые subagents для командного пайплайна Claude Code (PHP hexagonal).
+Role subagents for the Claude Code agent-team pipeline (PHP hexagonal).
 
 ## Analysis (on-demand)
 
-| Agent | Файл | Production-код |
-|-------|------|----------------|
+| Agent | File | Production code |
+|-------|------|-----------------|
 | Codebase analyzer | `codebase-analyzer.md` | no (explain-as-is only) |
 
 ## Roster (21)

package/presets/claude/php-hexagonal/agents/task-router.md

@@ -17,19 +17,19 @@ You are a task router for a **PHP 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», «обнови PHP/Composer-Composer» | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer |
-| `perf-audit` | «производительность», «JFR/async-profiler», «медленно» | 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), «upgrade», «обнови PHP/Composer» (upgrade PHP/Composer) | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `perf-audit` | «производительность» (performance), «JFR/async-profiler», «медленно» (slow) | performance-auditor | <!-- i18n-keep: E4 -->
+| `review-only` | «ревью» (review), «review MR», «проверь diff» (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», «юнит» (unit), «покрой use case» (cover use case) | unit-test-planner → unit-test-generator, or unit-test-healer | <!-- i18n-keep: E4 -->
 | `e2e-only` / integration | «integration», «e2e», «HTTP controller tests», «integration DB fixtures» | **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` | «документация» (documentation), «README», «changelog» | task-analyst → tech-writer | <!-- i18n-keep: E4 -->
+| `refactor` | «рефакторинг» (refactoring), «без изменения поведения» (no behavior change) | task-analyst → feature-developer → build-verifier → code-reviewer | <!-- i18n-keep: E4 -->
+| `spike` | «исследуй» (investigate), «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 «PHP backend uses integration-test trio».
 

package/presets/claude/php-hexagonal/commands/README.md

@@ -1,13 +1,13 @@
 # `.claude/commands` (preset php-hexagonal)
 
-Определения slash-команд и on-demand сценариев. Копируются в `.claude/commands/` при `ai-rules init claude --preset php-hexagonal`.
+Slash-command definitions and on-demand scenarios. Copied to `.claude/commands/` on `ai-rules init claude --preset php-hexagonal`.
 
-| Файл | Назначение |
-|------|------------|
-| `task.md` | Единая точка входа: router → dynamic pipeline → первый agent |
-| `task-continue.md` | Продолжение после human gate / паузы по `pipeline.json` |
-| `feature-start.md` | Legacy analyst-only старт без router |
-| `feature-continue.md` | Legacy продолжение; для `pipeline.json` делегирует смысл `/task-continue` |
-| `technical-retro.md` | Фасилитация технического ретро, включая блок «Работа агентов» |
+| File | Purpose |
+|------|---------|
+| `task.md` | Unified entry point: router → dynamic pipeline → first agent |
+| `task-continue.md` | Continue after human gate / pause using `pipeline.json` |
+| `feature-start.md` | Legacy analyst-only start without router |
+| `feature-continue.md` | Legacy continue; with `pipeline.json` delegates to `/task-continue` semantics |
+| `technical-retro.md` | Facilitate a technical retro, including the “Agent work” block |
 
-См. также корневой `README.md` пресета — у Claude Code помимо `rules/` и `commands/` используются `skills/`, `agents/`, `hooks/`, `team/`.
+See also the preset root `README.md` — Claude Code uses `skills/`, `agents/`, `hooks/`, and `team/` in addition to `rules/` and `commands/`.

package/presets/claude/php-hexagonal/commands/feature-continue.md

@@ -3,25 +3,25 @@ name: feature-continue
 description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
 ---
 
-# Feature continue — продолжение после утверждения brief
+# Feature continue — resume after brief approval
 
-Legacy-команда для продолжения после human gate. Для новых пайплайнов с `pipeline.json` используй те же правила, что в `/task-continue`.
+Legacy command to continue after a human gate. For new pipelines with `pipeline.json`, use the same rules as `/task-continue`.
 
-## Аргументы
+## Arguments
 
-`<slug>` — идентификатор задачи из `.claude/team/tasks/<slug>/`.
+`<slug>` — task id under `.claude/team/tasks/<slug>/`.
 
 ## Preconditions
 
-1. Прочитай `.claude/team/tasks/<slug>/brief.md` и `decomposition.md`.
-2. Если есть `pipeline.json`, делегируй поведение `/task-continue <slug>`.
-3. Если `pipeline.json` нет, прочитай `status.json`. Продолжай только если:
+1. Read `.claude/team/tasks/<slug>/brief.md` and `decomposition.md`.
+2. If `pipeline.json` exists, delegate behavior to `/task-continue <slug>`.
+3. If there is no `pipeline.json`, read `status.json`. Continue only if:
    - `phase` is `analysis` and `state` is `awaiting_approval` (user explicitly approved via this command), **or**
    - `phase` is `development`/`review`/`testing` and work should resume.
 
-## Legacy алгоритм без `pipeline.json`
+## Legacy algorithm without `pipeline.json`
 
-1. Обнови `status.json`:
+1. Update `status.json`:
    ```json
    {
      "slug": "<slug>",
@@ -30,22 +30,22 @@ Legacy-команда для продолжения после human gate. Дл
      "updatedAt": "<ISO8601>"
    }
    ```
-   Затем сразу установи `"state": "in_progress"` перед вызовом developer.
+   Then immediately set `"state": "in_progress"` before calling the developer.
 
-2. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+2. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
 
-3. Вызови subagent **feature-developer** с контекстом:
-   - пути к `brief.md`, `decomposition.md`, `status.json`;
-   - указание следовать `rules/architecture/feature-delivery-workflow.md`.
+3. Call subagent **feature-developer** with context:
+   - paths to `brief.md`, `decomposition.md`, `status.json`;
+   - instruction to follow `rules/architecture/feature-delivery-workflow.md`.
 
-4. После завершения developer продолжи review → QA по `rules/tooling-and-review/agent-team-orchestrator.md`.
+4. After the developer finishes, continue review → QA per `rules/tooling-and-review/agent-team-orchestrator.md`.
 
-## Если review вернул changes_requested
+## If review returned changes_requested
 
-- Верни `phase` в `development`, `state` в `in_progress`.
-- Снова вызови **feature-developer** с списком правок от reviewer.
+- Set `phase` back to `development`, `state` to `in_progress`.
+- Call **feature-developer** again with the reviewer’s change list.
 
-## Не делать
+## Do not
 
-- Не пропускать human gate без явного `/feature-continue`.
-- Не совмещать роли developer и reviewer в одном subagent-вызове.
+- Skip the human gate without an explicit `/feature-continue`.
+- Combine developer and reviewer roles in one subagent call.

package/presets/claude/php-hexagonal/commands/feature-start.md

@@ -3,28 +3,28 @@ name: feature-start
 description: Legacy analyst-only feature intake. Prefer /task for new work because it uses router and dynamic pipeline.
 ---
 
-# Feature start — legacy команда агентов
+# Feature start — legacy agent-team command
 
-Запуск **фазы анализа** для новой задачи. Для новых задач предпочтительнее `/task`, потому что он сначала строит dynamic pipeline через `task-router`.
+Starts the **analysis phase** for a new task. For new work prefer `/task`, because it builds a dynamic pipeline through `task-router` first.
 
-## Что делать
+## What to do
 
-1. Извлеки описание задачи из аргументов команды (всё после `/feature-start`).
-2. Сгенерируй **slug** (kebab-case, до 48 символов) из заголовка задачи.
-3. Создай `.claude/team/tasks/<slug>/` если его ещё нет — через запись файла (Write / Edit), не через Shell `mkdir`.
-4. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Вызови subagent **task-analyst** с полным описанием задачи и путём к артефактам.
-6. Дождись завершения аналитика. **Не вызывай 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 `.claude/team/tasks/<slug>/` if it does not exist yet — by writing a file (Write / Edit), not Shell `mkdir`.
+4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+5. Invoke subagent **task-analyst** with the full task description and artifact paths.
+6. Wait for the analyst to finish. **Do not invoke developer** at this stage.
 
 ## Human gate
 
-После аналитика:
+After the analyst:
 
-- Покажи пользователю ссылки на `brief.md` и `decomposition.md`.
-- Попроси проверить и утвердить или прислать правки.
-- Для продолжения: `/feature-continue <slug>` или `/task-continue <slug>`.
+- Show the user links to `brief.md` and `decomposition.md`.
+- Ask them to review and approve or send edits.
+- To continue: `/feature-continue <slug>` or `/task-continue <slug>`.
 
-## Если slug уже существует
+## If slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или `/feature-continue`.
-- Если задача в работе — спроси, продолжать или начать новый slug.
+- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
+- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/php-hexagonal/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. Прочитай `.claude/team/tasks/<slug>/pipeline.json` и `status.json`.
-2. Продолжай если:
-   - `awaitingHumanGate: true` или `state: awaiting_approval`, **или**
-   - `state: changes_requested` (после review), **или**
-   - задача прервана и нужно возобновить с `pipelineIndex`.
+1. Read `.claude/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`.
 
-## Алгоритм
+## Procedure
 
-1. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+1. Write `.claude/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/claude/php-hexagonal/commands/task.md

@@ -3,52 +3,52 @@ name: task
 description: Route a natural-language task through the agent-team pipeline: task-router, pipeline.json, and the first planned specialist.
 ---
 
-# Task — единая точка входа
+# Task — unified entry point
 
-Главная команда для постановки задачи в Claude Code. Родительский агент = оркестратор (`rules/tooling-and-review/agent-team-orchestrator.md`). Intake — `rules/tooling-and-review/agent-team-intake.md`.
+Main command for task intake in Claude Code. Parent agent = orchestrator (`rules/tooling-and-review/agent-team-orchestrator.md`). Intake — `rules/tooling-and-review/agent-team-intake.md`.
 
-## Аргументы
+## Arguments
 
-Всё после `/task` — описание задачи на естественном языке.
+Everything after `/task` is the task description in natural language.
 
-Примеры:
+Examples:
 
-- `/task Добавить use case отмены заказа`
-- `/task Handler падает при пустом body — пофикси`
-- `/task CI упал на composer test / composer test в PR`
-- `/task Миграция на новый PHP / обновление Composer-Composer модуля`
-- `/task Покрой unit-тестами OrderService`
-- `/task Напиши changelog для релиза фильтров`
-- `/task Сделай ревью моих изменений в application/`
-- `/task Напиши integration tests для persistence adapter`
+- `/task Добавить use case отмены заказа` (Add cancel-order use case) <!-- i18n-keep: E4 -->
+- `/task Handler падает при пустом body — пофикси` (Handler crashes on empty body — fix it) <!-- i18n-keep: E4 -->
+- `/task CI упал на composer test / composer test в PR` (CI failed on composer test in PR) <!-- i18n-keep: E4 -->
+- `/task Миграция на новый PHP / обновление Composer модуля` (Migrate to new PHP / update Composer module) <!-- i18n-keep: E4 -->
+- `/task Покрой unit-тестами OrderService` (Cover OrderService with unit tests) <!-- i18n-keep: E4 -->
+- `/task Напиши changelog для релиза фильтров` (Write changelog for filters release) <!-- i18n-keep: E4 -->
+- `/task Сделай ревью моих изменений в application/` (Review my changes in application/) <!-- i18n-keep: E4 -->
+- `/task Напиши integration tests для persistence adapter` (Write integration tests for persistence adapter) <!-- i18n-keep: E4 -->
 
-## Алгоритм
+## Procedure
 
-1. **Slug** — kebab-case из описания (≤48 символов). Создай `.claude/team/tasks/<slug>/` через запись файла (Write / Edit); runtime/hook владеет `status.json` — **не** полагайся на Shell `mkdir` как единственный способ создать каталог.
-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 `.claude/team/tasks/<slug>/` by writing a file (Write / Edit); runtime/hook owns `status.json` — **do not** rely on Shell `mkdir` as the only way to create the directory.
+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 router:
+   - confirm `pipeline.json` and `active-task.json`;
+   - **do not** write lifecycle fields in `status.json` / `metrics.json` yourself — orchestration runtime/hook owns them (see **agent-artifact-contracts**). If `status.json` is missing, only minimal bootstrap is allowed (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **do not** increment `pipelineIndex` manually;
+   - invoke 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 handoff (or until there is a `followup_message` from the hook).
+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.
+- Invoke developer before router and (if in pipeline) analyst/architect.
+- Hardcode role order — only `pipeline.json`.
+- Skip human gate without explicit continue.
 
-## Если slug занят
+## If 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; for new tasks prefer `/task`.
 
 ## Metrics