dirigent-skills

Use when resolving git merge/rebase/cherry-pick conflicts — especially resolving "all in favor of one side", resolving with a script or bulk command, or resolving multiple conflict blocks in one file. Also use before committing any conflict resolution, and when reviewing a merge someone (or some agent) claims is done. Triggers — "разреши конфликт", merge conflict markers, checkout --theirs/--ours, "возьми вариант ветки X".

Use when writing a task prompt (наряд) for a subagent that runs with worktree isolation, or any isolated working copy — especially when the prompt must include concrete commands, test invocations, or file paths. Also use when reviewing why an "isolated" agent ended up mutating the main checkout. Triggers — isolation:"worktree", "работай в worktree", составление наряда исполнителю с изоляцией, npm --prefix in a dispatch prompt.

Use when solving any non-trivial task in this ecosystem — before doing it by hand; when skill matching returns weak/none; when a used skill misfired or felt inadequate; when the same class of task keeps coming back; when tempted to say "there's no skill for this, I'll just do it by hand". Триггеры (RU) — «найди скилл», «нет подходящего скилла», «сделаю руками», повторная задача одного класса, провал скилла.

Use immediately after every npm publish (or any registry release), before closing the release task, announcing, or reporting success — including when publish exited 0, local tests were green, and it is late. Also use when a published CLI behaves differently via npx than locally, or prints nothing with exit 0. Triggers — "publish прошла?", "релиз готов", closing a release checklist item, npx silence.

Assembling analytical docx/pptx documents in Russian — comparative analysis, due diligence, counterparty checks, explanatory notes, partner profiles, shortlists. No pandoc table of contents; bordered tables with background-fill semantics; two tones (internal / external). Триггеры (RU) — «аналитика», «DD», «due diligence», «сравнительный», «пояснительная записка», «профиль партнёра», «таблицы с рамками», «без оглавления». Do NOT use for simple business letters/memos — use docx-ru.

Use when creating, editing, or exporting Russian business documents (docx/pdf) — proposals (КП), memos (справка), reports (отчёт), letters (письмо), memoranda, contract appendices, counterparty document packages. Триггеры (RU) — «сделай docx», «оформи документ», «деловой текст», «собери комплект», «выгрузи в word/PDF». Always applies a fixed Russian business formatting standard: Times New Roman, black text, Russian terminology, «Оглавление» (not "Table of Contents"), a pre-send checklist. Do NOT use for analytical/DD documents with semantic table formatting — use docx-analytical-ru.

Use BEFORE launching any loop — /loop, a background agent, or an autonomous run. Триггеры (RU) — «спроектируй цикл», «зациклить задачу», «автономный прогон», «крути пока не готово», «запусти в цикле». Also triggers on "design a loop", "loop harness", "run until done". Do NOT use for a single re-run of a command — only for recurring/autonomous execution. Plain `/loop` runs a loop; `looper` designs it first.

Sync session work into GitHub issues and query cross-repo track status. Use when ending a work session with changes worth recording, or when asked about the state of a track/issue across repositories. Triggers on "/manager", "sync session", "обнови issues", "синкни сессию", "зафиксируй прогресс", "статус задачи», «что по <track>», "track status", "what about <track>". Do NOT use for creating brand-new project plans — only for recording/reading existing work.

Use at the start of any non-trivial task in a multi-agent/multi-engine setup — to see who did what, at what stage, and what's still open or broken — and throughout the work, to record steps, failures, and results, so any other agent or engine can pick up the context. Триггеры (RU) — «worklog», «летопись», «журнал работ», «что делалось / на какой стадии», перед началом задачи, при сбое, при сдаче. Cross-engine shared journal for teams running several AI engines/agents against the same codebase or project.

Use before claiming any task is finished or telling the user "done". Триггеры (RU) — момент завершения работы, перед словами «сделал/готово/работает». Enforces verification-before-completion — run the actual check (tests, build, the command, open the file) and read its real output before reporting done. Applies to code AND to documents/configs.