@bonesofspring/ai-rules 0.2.14 → 0.2.16

package/presets/cursor/java/rules/preset-layering.mdc

@@ -9,29 +9,28 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-layering.md -->
 
-
 # Preset layering
 
-Правила для **авторов пресетов** (`packages/ai-rules/presets/**`). Не always-on в consumer apps.
+Rules for **preset authors** (`packages/ai-rules/presets/**`). Not always-on in consumer apps.
 
-## Слои
+## Layers
 
-| Слой | Где | Что класть |
-|------|-----|------------|
-| **Core** | `presets/_shared/core/**` | Stack-agnostic prose + checklists; без frontmatter; без путей `app/**`, `Features/**`, Playwright, xcodebuild |
-| **Stack** | `presets/{cursor\|claude}/<stack>/` | Domain/tooling, always-on trio стека, stack examples в **Stack notes** |
+| Layer | Where | What to put |
+|-------|-------|-------------|
+| **Core** | `presets/_shared/core/**` | Stack-agnostic prose + checklists; no frontmatter; no paths `app/**`, `Features/**`, Playwright, xcodebuild |
+| **Stack** | `presets/{cursor\|claude}/<stack>/` | Domain/tooling, stack always-on trio, stack examples in **Stack notes** |
 | **Platform** | Cursor `.mdc` / Claude `.md` | Frontmatter (`alwaysApply`/`globs` vs `paths:`), platform-only (`BUGBOT.md`, `CLAUDE.md`) |
 
-## Куда класть новое правило
+## Where to put a new rule
 
-1. Общие принципы для всех стеков → **core** + адаптеры с `<!-- shared-core: … -->`.
-2. Только один из installable стеков (`next` / `nuxt` / `svelte` / `ios-swift` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (не в `_shared`).
-3. Только Cursor или только Claude packaging → platform artifact / frontmatter, не дублировать семантику.
+1. Shared principles for all stacks → **core** + adapters with `<!-- shared-core: … -->`.
+2. Only one of the installable stacks (`next` / `nuxt` / `svelte` / `ios-swift` / `android-kotlin` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (not in `_shared`).
+3. Only Cursor or only Claude packaging → platform artifact / frontmatter; do not duplicate semantics.
 
 ## SoT
 
 - Packages path — SoT; root `.cursor/` — dogfood sync.
 - Per stack: **Cursor** `presets/cursor/<stack>/` → Claude twin same PR.
-- `_shared` **не** `--preset` и не копируется CLI `init`.
+- `_shared` is **not** a `--preset` and is not copied by CLI `init`.
 
-См. также: `preset-twin-sync`, `preset-token-budget`, `preset-pr-checklist`, `preset-no-cross-stack-leakage`.
+See also: `preset-twin-sync`, `preset-token-budget`, `preset-pr-checklist`, `preset-no-cross-stack-leakage`.

package/presets/cursor/java/rules/preset-no-cross-stack-leakage.mdc

@@ -9,18 +9,18 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-no-cross-stack-leakage.md -->
 
-
 # Preset no cross-stack leakage
 
-Запрет протекания stack-specific имён, путей и handoff stems между пресетами.
+Ban leakage of stack-specific names, paths, and handoff stems across presets.
 
 ## Principles
 
-- `next` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `nuxt` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `svelte` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `ios-swift` must not ship Playwright handoffs or Next lint recipes as required commands.
-- `go` / `java` / `php-hexagonal` / `php-laravel` / `mcp-ts` must not ship Playwright, XCUITest, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
+- `next` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `nuxt` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `svelte` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `ios-swift` must not ship Playwright handoffs, Android `instrumentation-test-*` handoffs, or Next lint recipes as required commands.
+- `android-kotlin` must not ship Playwright, XCUITest, `xcodebuild`, or Next lint recipes as required handoffs.
+- `go` / `java` / `php-hexagonal` / `php-laravel` / `mcp-ts` must not ship Playwright, XCUITest, Android instrumentation agents, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
 - `mcp-ts` must not ship Go tool commands (`go test`, `go vet`, `golangci-lint`) or `integration-test-*` agents as required delivery gates.
 - Shared core must not embed stack paths (`app/src/**`, `Features/**`, `playwright`, `xcodebuild`).
 
@@ -29,25 +29,37 @@ alwaysApply: false
 In ios-swift `chain-team-phases.sh` / agent handoffs (Cursor + Claude):
 
 - `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`
+- `instrumentation-test-` as required Android handoffs
 - `app/__tests__/e2e` as a required path
 - Positive yarn recipes `lint:js` / `lint:css` as commands to run (negation prose alone is weak — prefer zero occurrences)
 
 Required instead: `xcuitest-test-*` stems; build-verifier mentions `xcodebuild` or `post-change-build` / `xcode-tooling`.
 
+## Forbidden in android-kotlin hooks/agents (FAIL)
+
+In android-kotlin `chain-team-phases.sh` / agent handoffs (Cursor + Claude):
+
+- `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`
+- `app/__tests__/e2e` as a required path
+- `xcuitest-test-`, positive `xcodebuild` / `SwiftLint` as required handoffs
+- Positive yarn recipes `lint:js` / `lint:css` as commands to run
+
+Required instead: `instrumentation-test-*` stems; build-verifier mentions `gradle-tooling` and/or `post-change-build` (Gradle wrapper discovery — not `xcodebuild` as the default gate).
+
 ## Forbidden in next hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Next app work
 
 ## Forbidden in nuxt hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Nuxt app work
 - Frontend profile mirrors `next`: Playwright / `lint:js` / `lint:css` allowed
 
 ## Forbidden in svelte hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for SvelteKit app work
 - Frontend profile mirrors `next` / `nuxt`: Playwright / `lint:js` / `lint:css` allowed
 
@@ -57,7 +69,7 @@ Shared backend-stack bans (`go`, `java`, `php-hexagonal`, and `php-laravel`):
 
 - `playwright-test-`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`
 - Positive yarn recipes `lint:js` / `lint:css`
-- `xcuitest-test-`, `xcodebuild`, `SwiftLint` as required handoffs
+- `xcuitest-test-`, `instrumentation-test-`, `xcodebuild`, `SwiftLint` as required handoffs
 - Agent file `accessibility-reviewer` (no UI surface)
 
 Required instead: `integration-test-*`; build-verifier / `post-change-test` plus stack tooling — `go-tooling` (`go test`, `go vet`), `java-tooling` (`mvn test` / `./gradlew test`), or `php-tooling` (`php artisan test` / `composer test` / `vendor/bin/phpunit`).
@@ -68,9 +80,9 @@ Same UI/mobile bans as backend stacks, plus:
 
 - `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`
 - Positive yarn recipes `lint:js` / `lint:css` as required gates
-- `xcuitest-test-`, `xcodebuild`, `SwiftLint` as required handoffs
+- `xcuitest-test-`, `instrumentation-test-`, `xcodebuild`, `SwiftLint` as required handoffs
 - Go tool commands as required MCP delivery gates: `go test`, `go vet`, `golangci-lint`
-- Agent files: `playwright-test-*`, `xcuitest-test-*`, `integration-test-*`, `accessibility-reviewer`
+- Agent files: `playwright-test-*`, `xcuitest-test-*`, `instrumentation-test-*`, `integration-test-*`, `accessibility-reviewer`
 
 Required instead: package-manager–discovered typecheck/test (`mcp-ts-tooling`, `post-change-test`); Phase 1 gates `build-verifier` + `security-reviewer`.
 
@@ -81,4 +93,4 @@ Required instead: package-manager–discovered typecheck/test (`mcp-ts-tooling`,
 
 ## Chain fork
 
-`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `nuxt`, `svelte`, `ios-swift`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).
+`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `nuxt`, `svelte`, `ios-swift`, `android-kotlin`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).

package/presets/cursor/java/rules/preset-pr-checklist.mdc

@@ -9,19 +9,18 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-pr-checklist.md -->
 
-
 # Preset PR checklist
 
-Чеклист для PR, затрагивающих `packages/ai-rules/presets/**` (и dogfood `.cursor/` sync).
+Checklist for PRs that touch `packages/ai-rules/presets/**` (and dogfood `.cursor/` sync).
 
 ## Before merge
 
-- [ ] **SoT:** правки в `packages/…` (не только root `.cursor/`)
-- [ ] **Core:** если менялся `_shared/core/**` — обновлены все `<!-- shared-core: … -->` consumers (или documented intentional fork)
-- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel — см. `preset-twin-sync`)
-- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table актуален
+- [ ] **SoT:** edits in `packages/…` (not only root `.cursor/`)
+- [ ] **Core:** if `_shared/core/**` changed — all `<!-- shared-core: … -->` consumers updated (or documented intentional fork)
+- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, android-kotlin, go, java, mcp-ts, php-hexagonal, and php-laravel — see `preset-twin-sync`)
+- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table is current
 - [ ] **Token budget:** alwaysApply / session-start ≤ 3; meta rules not always-on
-- [ ] **Leakage:** нет чужих stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
+- [ ] **Leakage:** no foreign stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
 - [ ] **Twin depth:** domain ≥15 lines; thin aliases documented
 - [ ] **README:** stack `rules/README.md` core→stack mapping / catalog updated if stems added
 - [ ] **CHANGELOG / package README:** note when public preset paths or install surface change

package/presets/cursor/java/rules/preset-token-budget.mdc

@@ -9,21 +9,20 @@ alwaysApply: false
 
 <!-- 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/cursor/java/rules/preset-twin-sync.mdc

@@ -9,7 +9,6 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-twin-sync.md -->
 
-
 # Preset twin sync
 
 Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
@@ -27,6 +26,7 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 | `mcp-ts` | `presets/cursor/mcp-ts/rules/*.mdc` | `presets/claude/mcp-ts/rules/<topic>/` | Keep in `claude/mcp-ts/rules/README.md` |
 | `php-hexagonal` | `presets/cursor/php-hexagonal/rules/*.mdc` | `presets/claude/php-hexagonal/rules/<topic>/` | Keep in `claude/php-hexagonal/rules/README.md` |
 | `php-laravel` | `presets/cursor/php-laravel/rules/*.mdc` | `presets/claude/php-laravel/rules/<topic>/` | Keep in `claude/php-laravel/rules/README.md` |
+| `android-kotlin` | `presets/cursor/android-kotlin/rules/*.mdc` | `presets/claude/android-kotlin/rules/<topic>/` | Keep in `claude/android-kotlin/rules/README.md` |
 
 ## Same-PR checklist
 
@@ -51,5 +51,6 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 - **mcp-ts:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java; mapping table required).
 - **php-hexagonal:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts; mapping table required).
 - **php-laravel:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts / php-hexagonal; mapping table required).
+- **android-kotlin:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts / php-*; mapping table required).
 
 Dogfood: sync packages → root `.cursor/` after Cursor SoT changes (not the reverse). Use `packages/ai-rules/scripts/sync-dogfood-cursor.sh`.

package/presets/cursor/java/rules/technical-retro.mdc

@@ -5,12 +5,12 @@ alwaysApply: false
 
 <!-- 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/cursor/java/team/README.md

@@ -1,6 +1,6 @@
 # Agent team artifacts (preset java)
 
-Каталог артефактов пайплайна «команда агентов» для Java backend (hexagonal / ports & adapters).
+Artifact directory for the agent-team pipeline for Java backends (hexagonal / ports & adapters).
 
 ## Layout
 

package/presets/cursor/mcp-ts/AGENTS.md

@@ -2,12 +2,12 @@
 
 **Repo-root agents:** see [`AGENTS.md`](../../AGENTS.md) at the project root (cross-tool setup, commands, security, living conventions pointers).
 
-| Задача | Куда смотреть |
-|--------|----------------|
-| Новая work-задача | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
-| Фича end-to-end | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
-| Стек и границы | `mcp-ts-app-core.mdc`, `mcp-server-boundaries.mdc` |
-| После правок TS | `post-change-test.mdc` (+ `mcp-ts-tooling.mdc`) |
+| Task | Where to look |
+|------|----------------|
+| New work request | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
+| End-to-end feature | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
+| Stack and boundaries | `mcp-ts-app-core.mdc`, `mcp-server-boundaries.mdc` |
+| After TS edits | `post-change-test.mdc` (+ `mcp-ts-tooling.mdc`) |
 | Tool/schema design | `mcp-tool-design.mdc`, `mcp-contract-testing.mdc` |
 | Code review | skill `code-review` + `code-review-mr.mdc` |
 | Security | `security-mcp.mdc` + agent `security-reviewer` |

package/presets/cursor/mcp-ts/MCP.md

@@ -1,11 +1,11 @@
 # MCP (preset `mcp-ts`, Cursor)
 
-Копируется в `.cursor/mcp.json` при `ai-rules init cursor --preset mcp-ts`.
+Copied to `.cursor/mcp.json` on `ai-rules init cursor --preset mcp-ts`.
 
 ## Servers (active in shipped config)
 
-| Name | Package | Зачем |
-|------|---------|--------|
+| Name | Package | Purpose |
+|------|---------|---------|
 | `context7` | `@upstash/context7-mcp@3.2.5` (pinned in `mcp.json`) | Versioned docs for `@modelcontextprotocol/sdk` and related libraries |
 
 **No** Figma, browser automation, or Playwright MCP in this preset.
@@ -32,6 +32,6 @@ Shipped `mcp.json` pins `@upstash/context7-mcp@<version>` so `init` does not pul
 
 Adjust `command`/`args` to the project's `bin` / `npx` entry after packaging. Prefer stdio for local Cursor/Claude use.
 
-Секреты в файл не кладём. Опционально: `CONTEXT7_API_KEY` в окружении.
+Do not put secrets in the file. Optional: `CONTEXT7_API_KEY` in the environment.
 
-После init: Settings → MCP → включить серверы. `init` перезаписывает одноимённый MCP config.
+After init: Settings → MCP → enable servers. `init` overwrites the same-named MCP config.

package/presets/cursor/mcp-ts/agents/task-router.md

@@ -17,12 +17,12 @@ You are a task router for a **TypeScript MCP server** agent team. You **do not**
 
 | intent | Signals | Default steps |
 |--------|---------|---------------|
-| `feature` | «добавь tool», «новая», «реализуй», schema/handler | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `bugfix` | «баг», «fix», «не работает», «падает» | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `review-only` | «ревью», «review MR», «проверь diff» | `security-reviewer` for threat/capability/auth/secrets diffs; **plus** parent applies skill `code-review` (write `review.md`) — no `code-reviewer` agent in Phase 1. Pure schema/style-only diffs: skip security step, parent skill only (document in `skipped`) |
-| `spike` | «исследуй», «spike», proof of concept | task-analyst → solution-architect |
-| `refactor` | «рефакторинг», «без изменения поведения» | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `retro` | «ретро», «postmortem» | (orchestrator → `/technical-retro`) |
+| `feature` | "add tool", "new", "implement", schema/handler | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `bugfix` | "bug", "fix", "doesn't work", "crashes" | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `review-only` | "review", "review MR", "check diff" | `security-reviewer` for threat/capability/auth/secrets diffs; **plus** parent applies skill `code-review` (write `review.md`) — no `code-reviewer` agent in Phase 1. Pure schema/style-only diffs: skip security step, parent skill only (document in `skipped`) |
+| `spike` | "investigate", "spike", proof of concept | task-analyst → solution-architect |
+| `refactor` | "refactor", "no behavior change" | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `retro` | "retro", "postmortem" | (orchestrator → `/technical-retro`) |
 
 ### Security-reviewer routing
 
@@ -38,7 +38,7 @@ Append **`security-reviewer` after `build-verifier`** for `feature` / `bugfix` /
 
 **Phase 1 available agents only:** `task-router`, `task-analyst`, `solution-architect`, `feature-developer`, `build-verifier`, `security-reviewer`.
 
-**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), `accessibility-reviewer`, `integration-test-*`, or Phase 2 `contract-test-*`. Put them in `skipped` with reason «mcp-ts Phase 1 roster».
+**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), `accessibility-reviewer`, `integration-test-*`, or Phase 2 `contract-test-*`. Put them in `skipped` with reason "mcp-ts Phase 1 roster".
 
 ## Pipeline profiles
 

package/presets/cursor/mcp-ts/commands/README.md

@@ -1,6 +1,6 @@
 # Commands (mcp-ts)
 
-Slash-команды копируются в `.cursor/commands/` (Cursor) или `.claude/commands/` (Claude) при `ai-rules init … --preset mcp-ts`.
+Slash commands are copied to `.cursor/commands/` (Cursor) or `.claude/commands/` (Claude) on `ai-rules init … --preset mcp-ts`.
 
 | Command | Purpose |
 |---------|---------|

package/presets/cursor/mcp-ts/commands/feature-continue.md

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

package/presets/cursor/mcp-ts/commands/feature-start.md

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

package/presets/cursor/mcp-ts/commands/task-continue.md

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

package/presets/cursor/mcp-ts/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 — единая точка входа (router + pipeline)
+# Task — unified entry point (router + pipeline)
 
-Главная команда для постановки задачи. Родительский агент = оркестратор (`agent-team-orchestrator.mdc`). Intake для work-запросов без `/task` — `agent-team-intake.mdc`.
+Main command for task intake. Parent agent = orchestrator (`agent-team-orchestrator.mdc`). Intake for work requests without `/task` — `agent-team-intake.mdc`.
 
-## Аргументы
+## Arguments
 
-Всё после `/task` — описание задачи на естественном языке.
+Everything after `/task` is the task description in natural language.
 
-Примеры:
+Examples:
 
-- `/task Добавить MCP tool list_resources`
-- `/task Handler падает при пустом body — пофикси`
-- `/task Project tests падают локально после правки schema — bugfix + build-verifier`
-- `/task Миграция на новый SDK / package`
-- `/task Покрой unit-тестами handler echo`
-- `/task Напиши changelog для релиза tool`
-- `/task Сделай ревью моих изменений в src/tools`
-- `/task Напиши contract/unit tests для tool schema`
+- `/task Add MCP tool list_resources`
+- `/task Handler crashes on empty body — fix it`
+- `/task Project tests fail locally after schema change — bugfix + build-verifier`
+- `/task Migrate to a new SDK / package`
+- `/task Cover handler echo with unit tests`
+- `/task Write changelog for tool release`
+- `/task Review my changes in src/tools`
+- `/task Write contract/unit tests for tool schema`
 
-## Алгоритм
+## Procedure
 
-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 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