@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/presets/claude/ios-swift/MCP.md

@@ -1,14 +1,16 @@
-# MCP (preset `ios-swift`, Claude Code)
+# MCP (preset `ios-swift`, Claude)
 
-Копируется в **корень проекта** как `.mcp.json` при `ai-rules init claude --preset ios-swift`.
+Copied to `.claude/mcp.json` on `ai-rules init cursor --preset ios-swift`.
 
 ## Servers
 
-| Name | Package | Зачем |
-|------|---------|--------|
-| `context7` | `@upstash/context7-mcp` | Актуальная документация Swift / SwiftUI / Apple frameworks |
-| `figma` | remote `https://mcp.figma.com/mcp` | Design context → SwiftUI; OAuth при первом подключении |
+| Name | Package | Purpose |
+|------|---------|---------|
+| `context7` | `@upstash/context7-mcp` | Up-to-date Swift / SwiftUI / Apple frameworks docs |
+| `figma` | remote `https://mcp.figma.com/mcp` | Design context → SwiftUI; OAuth in the Claude Code / MCP client |
 
-Playwright / Chrome DevTools не входят в ios-пресет.
+Playwright / Chrome DevTools are **not** part of the ios preset (browser e2e is forbidden for the agent team).
 
-Секреты не коммитим. Опционально: `CONTEXT7_API_KEY`. Figma — OAuth. Approve project MCP через `/mcp`.
+Do not put secrets in the file. Optional: `CONTEXT7_API_KEY` in the environment. Figma — OAuth (do not commit the token).
+
+After init: enable MCP servers in the client. `init` overwrites a same-named `.mcp.json`.

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

@@ -1,19 +1,19 @@
 # Preset `ios-swift` (Claude Code)
 
-Правила и agent-team surface для Swift / SwiftUI / XCTest / XCUITest.
+Rules and agent-team surface for Swift / SwiftUI / XCTest / XCUITest.
 
-Структура: topic folders под `rules/` + agents/skills/commands/hooks/team (как next Claude).
+Layout: topic folders under `rules/` + agents/skills/commands/hooks/team (like next Claude).
 
-| В пресете | Куда копирует `ai-rules init claude --preset ios-swift` |
+| In the preset | Where `ai-rules init claude --preset ios-swift` copies |
 |-----------|---------------------------------------------------------|
 | `CLAUDE.md` | `.claude/CLAUDE.md` |
 | `rules/**` | `.claude/rules/**` |
 | `commands/**` | `.claude/commands/**` |
-| `skills/**` | `.claude/skills/**` (**7**, в т.ч. `xcuitest-e2e`) |
+| `skills/**` | `.claude/skills/**` (**7**, incl. `xcuitest-e2e`) |
 | `agents/**` | `.claude/agents/**` (**22**, XCUITest trio + `codebase-analyzer`) |
-| `hooks/**` | `.claude/hooks/**` (scripts + README; **нет** `hooks.json`) |
+| `hooks/**` | `.claude/hooks/**` (scripts + README; **no** `hooks.json`) |
 | `team/**` | `.claude/team/**` |
-| `mcp.json` | **`.mcp.json`** в корне (Context7 + Figma) |
+| `mcp.json` | **`.mcp.json`** at repo root (Context7 + Figma) |
 | `MCP.md` | `.claude/MCP.md` |
 
 ```bash
@@ -29,14 +29,14 @@ npx @bonesofspring/ai-rules init claude --preset ios-swift
 
 ## Session-start (= Cursor alwaysApply)
 
-Ровно **3** файла без `paths:`: `stack/ios-app-core.md`, `architecture/boundaries.md`, `tooling-and-review/code-quality.md`. Бюджет тела ≤140 строк суммарно.
+Exactly **3** files without `paths:`: `stack/ios-app-core.md`, `architecture/boundaries.md`, `tooling-and-review/code-quality.md`. Body budget ≤140 lines total.
 
 ## Parity with Cursor
 
 - **SoT:** `presets/cursor/ios-swift/`
 - Change Cursor → update Claude twin **same PR**
 - Mapping: [`rules/README.md`](./rules/README.md)
-- **`BUGBOT.md`:** Cursor-only (нет twin); review в Claude — skill `code-review` + `tooling-and-review/code-review.md`
+- **`BUGBOT.md`:** Cursor-only (no twin); review in Claude — skill `code-review` + `tooling-and-review/code-review.md`
 
 ## Cross-tool root AGENTS
 

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

@@ -1,6 +1,6 @@
 # `.claude/agents` (preset ios-swift)
 
-Ролевые subagents для командного пайплайна Cursor (iOS / Swift / SwiftUI).
+Role subagents for the Claude Code 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 |
@@ -26,25 +26,25 @@ When copying next pipeline templates: put Playwright stems in `skipped` with rea
 | qa-tester, unit-test-*, xcuitest-test-* | tests only |
 | tech-writer | docs only |
 
-## Frontmatter `readonly`
+## Team writes
 
-Все agents — **`readonly: false`** (нужна запись в `.claude/team/**`). Ограничения production — в теле промпта.
+Team agents may write under `.claude/team/**`. Production restrictions live in the prompt body.
 
 ## Model matrix (frontmatter `model`)
 
-Same tiers as **claude/next**. Defaults in this preset:
+Same tiers as **cursor/next** (see that README for full notes). Defaults in this preset:
 
 | Tier | Frontmatter | Agents |
 |------|-------------|--------|
 | **cheap** | `fast` | router, analyst, build-verifier, code-reviewer, tech-writer, codebase-analyzer |
 | **standard** | `inherit` | developer, debugger, ci-investigator, api-contract, a11y, qa, unit-*, xcuitest-* |
-| **strong** | `opus` | solution-architect, migration-specialist, security-reviewer, performance-auditor |
+| **strong** | `claude-opus-4-8[effort=high]` | solution-architect, migration-specialist, security-reviewer, performance-auditor |
 
-Optional `steps[].model`: `cheap` \| `standard` \| `strong`.
+Optional `steps[].model`: `cheap` \| `standard` \| `strong` (router/orchestrator policy — same as next).
 
 ## 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`.
 
 `steps[].model` optional: `cheap` \| `standard` \| `strong`.
 
-Копируется в `.claude/agents/` при `ai-rules init claude --preset ios-swift`.
+Copied to `.claude/agents/` on `ai-rules init claude --preset ios-swift`.

package/presets/claude/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** `tooling-and-review/post-change-build.md` (+ `tooling-and-review/xcode-tooling.md` for commands). If next step is `build-verifier`, scoped build/lint on changed targets is enough.
 

package/presets/claude/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/claude/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
 
@@ -63,12 +63,12 @@ Keep top-level `profile` and emit this top-level object in every new `pipeline.j
 
 ## Model tiers (`steps[].model`)
 
-Optional: `"model": "cheap" | "standard" | "strong"`. Same policy as **claude/next** `task-router.md`:
+Optional: `"model": "cheap" | "standard" | "strong"`. Same policy as **cursor/next** `task-router.md`:
 
 - `light` → `cheap` on all steps (debugger unclear root cause → `strong`)
 - `full` / `spike` / security|perf specialists → `strong` on architect, migration, security, perf steps
 - never `strong` on build-verifier / tech-writer / task-router
-- omit on `standard` → agent frontmatter (`fast` / `inherit` / `opus`)
+- omit on `standard` → agent frontmatter (`fast` / `inherit` / `claude-opus-4-8[effort=high]`)
 
 Fixtures: `.claude/team/fixtures/` (feature-full, feature-light, bugfix-standard).
 

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

@@ -1,13 +1,51 @@
-# `.claude/commands` (preset ios-swift)
+# Claude commands (ios-swift preset)
 
-Определения slash-команд и on-demand сценариев. Копируются в `.claude/commands/` при `ai-rules init claude --preset ios-swift`.
+Slash commands are copied to `.claude/commands/` on `ai-rules init claude --preset ios-swift`.
 
-| Файл | Назначение |
-|------|------------|
-| `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` | Фасилитация технического ретро, включая блок «Работа агентов» |
+## Agent commands
 
-См. также корневой `README.md` пресета — у Claude Code помимо `rules/` и `commands/` используются `skills/`, `agents/`, `hooks/`, `team/`.
+| 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` examples
+
+```
+/task Add a date filter to Order History
+→ analyst → developer → reviewer → QA
+
+/task Order History crashes on an empty list
+→ debugger → developer → reviewer → QA (regression)
+
+/task CI failed on lint in PR #142
+→ ci-investigator → developer → reviewer
+
+/task Migrate to iOS Swift 15
+→ analyst → migration-specialist → developer → reviewer → QA
+
+/task Check accessibility of the payment modal
+→ analyst → developer → a11y-reviewer → code-reviewer
+
+/task Cover the orders mapper with unit tests
+→ unit-planner → unit-generator
+
+/task Write a README for the new filters feature
+→ analyst → tech-writer
+
+/task Review changes in Features/Orders
+→ reviewer only
+```
+
+## Related files
+
+- Subagents: `../agents/` (22 roles, including `task-router.md`, `codebase-analyzer.md`, and `xcuitest-test-{planner,generator,healer}`)
+- Orchestrator: `../rules/tooling-and-review/agent-team-orchestrator.md`
+- Skills: `../skills/` (`feature-delivery`, `code-review`, `debug-investigation`, `ci-investigation`, `unit-testing`, `xcuitest-e2e`, `technical-retro`)
+- Artifacts: `../team/README.md` (`pipeline.json`, `status.json`)
+- Hooks: `../hooks.json`, `../hooks/chain-team-phases.sh`
+
+Create and edit commands in this preset folder (Claude Code slash commands).

package/presets/claude/ios-swift/commands/feature-continue.md

@@ -3,49 +3,17 @@ name: feature-continue
 description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
 ---
 
-# Feature continue — продолжение после утверждения brief
+# Feature continue — legacy alias
 
-Legacy-команда для продолжения после human gate. Для новых пайплайнов с `pipeline.json` используй те же правила, что в `/task-continue`.
+> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
 
-## Аргументы
+Continue after a human gate. Full logic is in **`task-continue.md`**.
 
-`<slug>` — идентификатор задачи из `.claude/team/tasks/<slug>/`.
+## Short version
 
-## Preconditions
+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`.
 
-1. Прочитай `.claude/team/tasks/<slug>/brief.md` и `decomposition.md`.
-2. Если есть `pipeline.json`, делегируй поведение `/task-continue <slug>`.
-3. Если `pipeline.json` нет, прочитай `status.json`. Продолжай только если:
-   - `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`
-
-1. Обнови `status.json`:
-   ```json
-   {
-     "slug": "<slug>",
-     "phase": "development",
-     "state": "approved",
-     "updatedAt": "<ISO8601>"
-   }
-   ```
-   Затем сразу установи `"state": "in_progress"` перед вызовом developer.
-
-2. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-
-3. Вызови subagent **feature-developer** с контекстом:
-   - пути к `brief.md`, `decomposition.md`, `status.json`;
-   - указание следовать `rules/architecture/feature-delivery-workflow.md`.
-
-4. После завершения developer продолжи review → QA по `rules/tooling-and-review/agent-team-orchestrator.md`.
-
-## Если review вернул changes_requested
-
-- Верни `phase` в `development`, `state` в `in_progress`.
-- Снова вызови **feature-developer** с списком правок от reviewer.
-
-## Не делать
-
-- Не пропускать human gate без явного `/feature-continue`.
-- Не совмещать роли developer и reviewer в одном subagent-вызове.
+See `task-continue.md` for details and the handoff table.

package/presets/claude/ios-swift/commands/feature-start.md

@@ -3,28 +3,31 @@ 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 (analyst only)
 
-Запуск **фазы анализа** для новой задачи. Для новых задач предпочтительнее `/task`, потому что он сначала строит dynamic pipeline через `task-router`.
+> **Prefer:** `/task <description>` — the router chooses roles and order automatically.
 
-## Что делать
+Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `tooling-and-review/agent-team-orchestrator.md`).
 
-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** на этом этапе.
+## What to do
+
+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 `.claude/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
+4. Write `.claude/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`.
-- Попроси проверить и утвердить или прислать правки.
-- Для продолжения: `/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: `/task-continue <slug>` or `/feature-continue <slug>`.
 
-## Если slug уже существует
+## If the slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или `/feature-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/claude/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. Прочитай `.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`.
 
-## Алгоритм
+## Algorithm
 
-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/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 — единая точка входа
+# Task — single entry point
 
-Главная команда для постановки задачи в Claude Code. Родительский агент = оркестратор (`rules/tooling-and-review/agent-team-orchestrator.md`). Intake — `rules/tooling-and-review/agent-team-intake.md`.
+Main command for filing work 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 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 символов). Создай `.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); the 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 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