Agent Roster

The devops-plugin ships thirteen agents. Each is a Markdown file with YAML frontmatter (name, description, tools, model, permissionMode, isolation, background) followed by step-by-step workflow instructions. All agents default to model: sonnet, permissionMode: acceptEdits, and isolation: worktree.

Planning agents

feature-designer

Accepts a high-level project or feature brief from the user and produces two outputs: (1) a concise Markdown design document committed to docs/designs/<slug>.md in the target repo, and (2) a tree of YouTrack issues — one epic per module, with sub-issues for granular functions — filed by delegating to issue-creater.

Invocation trigger: user provides a fuzzy product-level brief and wants it decomposed into modules, functions, and a YouTrack issue tree.

Key rules: requires single-batch approval on the full plan before filing any issue; hard-coded size heuristic (split if ≥3 functions or ≥1 day of work per function); must never invoke issue-resolver, dispatcher, or task-runner.

tech-leader

Consumes a module-level epic produced by feature-designer, decides whether to split it, and creates up to three per-lane sub-issues — frontend, backend, designer — each with an explicit Interaction Contract section. Locks cross-lane API boundaries before any code is written.

Invocation trigger: user wants to split a module-level epic into frontend/backend/designer sub-issues with cross-lane interaction contracts.

Key rules: hard-coded split heuristic (split when ≥2 of: UI changes, data/API changes, visual design changes); backend lane contracts must include a Database Migrations subsection; never creates docs or infra lane sub-issues in v1.

issue-creater

Interactively plans and scopes work, then creates a well-structured YouTrack issue in project COR. Used by feature-designer and tech-leader in autonomous (non-interactive) mode.

issue-clarifier

Accepts a YouTrack issue ID and a Discord chat_id, iterates through ## Open Questions one question at a time via Discord, folds user answers back into the issue description, and posts prerequisite memos. Sits upstream of issue-resolver as the interactive clarification layer. Manually invoked only — issue-resolver must not auto-invoke it.

Core pipeline agents

issue-resolver

Orchestrator. Picks up a YouTrack issue assigned to Claude_Code, routes implementation to the appropriate specialist agent, then handles all branch, commit, PR, and YouTrack operations.

Routing priority chain:

flowchart TD
    %% issue-resolver routing priority
    A{Lane field set?} -->|yes| B[Route to lane specialist]
    A -->|no| C{Git Repo in map?}
    C -->|doc| D[doc-writer]
    C -->|monorepo| E[STOP - ask planner to split]
    C -->|other known repo| F[self-implement]
    C -->|unknown| G{Keyword sniff}
    G -->|mock/wireframe/visual| H[ui-designer]
    G -->|no match| F

Open Questions guard: if the issue description contains an ## Open Questions section with at least one non-empty bullet, issue-resolver blocks and exits — it does not start work until issue-clarifier resolves them.

pr-reviewer

Reviews PRs labeled Ready. Ticks verified task-list checkboxes in the PR body (mandatory step before approval). Approves and merges clean PRs; applies Need Changes and leaves actionable feedback otherwise. Sets Stage=Done on the YouTrack issue after merge. Deletes the source branch.

pr-resolver

Activates when a PR carries the Need Changes label. Reads review comments, applies fixes, commits, pushes, and re-labels the PR Ready.

pipeline

Chains issue-resolver → pr-reviewer → pr-resolver in a loop until Stage=Done or 5 iterations are exhausted. Sends Discord heartbeats at each stage. Reports exhaustion via YouTrack comment and Discord failure notification if the budget runs out.

dispatcher

Routes tasks to sub-project repos, creates per-task git worktrees, and dispatches concurrent pipeline subagents (max 5 at a time). Operates in explicit mode (specific issue ID supplied) or auto-consume mode (picks up Assignee=Claude_Code issues). Never performs implementation, review, or merge directly.

task-runner

For small, self-contained tasks that do not yet have a YouTrack issue. Creates the issue, resolves it, and drives the PR to merge in a single pass — no change-request looping.

Specialist agents

doc-writer

Writes and updates Markdown documentation in the doc repository (built with docfx). Produces Markdown files with docfx front matter (uid, title), Mermaid diagrams, and toc.yml updates. Invoked by issue-resolver when Git Repo=doc or Lane=docs.

csharp-backend-coder

Implements features and fixes in C# backend repositories following a 3-layer architecture (Repository → Service → Controller). Enforces EF Core patterns, async/await, DTOs, constructor injection, and strict layer separation. Invoked when Git Repo is a C# backend project or Lane=backend.

blazor-frontend-coder

Implements Blazor WebAssembly/Server frontend changes. Invoked when Lane=frontend.

ui-designer

Produces self-contained HTML visual mocks plus PNG screenshots for UI screens or features. Sits upstream of blazor-frontend-coder. Invoked when Lane=designer or issue keywords include mock, wireframe, or visual design.

repo-scaffolder

Generates and maintains per-repo CLAUDE.md and .claude/settings.json files. Manually invoked only — issue-resolver must not auto-invoke it.

chat-responder

Answers user questions with verified, source-backed responses via web search. No local file or MCP access.

Table of Contents