/edikt:agents

List, install, and manage specialist agent templates.

Usage

/edikt:agents
/edikt:agents add {slug}
/edikt:agents remove {slug}
/edikt:agents show {slug}
/edikt:agents suggest

What are specialist agents?

Specialist agents are role-based configurations installed in .claude/agents/. Each agent has a defined domain, trigger conditions that tell the model when to delegate to it, and constraints that keep it focused. No agent has a fixed model — the model is assigned per plan phase based on task complexity (see Model selection).

When the model sees a task that matches an agent's domain, it delegates automatically. You can also invoke any agent directly by name.

Available agents

edikt ships 18 domain specialist agents organized in four tiers.

Always installed

Agent	Domain
architect	System design, ADRs, component boundaries, trade-off analysis
docs	Documentation accuracy, gap detection, runbooks
qa	Testing strategy, test writing, coverage

Common (most projects)

Agent	Domain
sre	Reliability, observability, deployment, infrastructure
security	OWASP, auth, secrets, threat modeling
pm	Requirements, scope, user stories, PRDs
api	REST/GraphQL/gRPC contracts, versioning, breaking changes

Stack-triggered (installed when detected)

Agent	Triggered by
backend	Go, TypeScript, Python, PHP, Ruby, Java, Rust
frontend	TypeScript + React/Vue/Angular/Svelte/Next.js
dba	Go, Python, Java (database-heavy stacks)
ux	React, Next.js, Vue, Angular, Svelte, React Native, Flutter
platform	Docker, Kubernetes, Terraform
mobile	React Native, Flutter, Swift, Kotlin
seo	Next.js, web content projects
gtm	Web content projects
data	Data pipeline projects

Optional (available on request)

Agent	Domain
performance	Optimization, profiling, caching
compliance	HIPAA, PCI, SOC2, GDPR

Subcommands

No argument — list agents

/edikt:agents

Installed agents (11):
  architect   — System design, ADRs, trade-off analysis
  docs        — Documentation accuracy, gap detection
  qa          — Testing strategy, test writing, coverage
  sre         — Reliability, observability, deployment
  security    — OWASP, auth, secrets, threat modeling
  pm          — Requirements, scope, user stories
  api         — REST/GraphQL/gRPC contracts, versioning
  backend     — Backend implementation, business logic
  dba         — Schema, migrations, queries, data modeling
  ...

Available (not installed):
  performance — Performance profiling and optimization
  compliance  — HIPAA, PCI, SOC2, GDPR

/edikt:agents add performance

add {slug} — install an agent

/edikt:agents add performance

Copies the agent template from ~/.edikt/templates/agents/ to .claude/agents/. Commit the new file so your whole team gets it.

remove {slug} — uninstall an agent

/edikt:agents remove pm

Deletes .claude/agents/{slug}.md.

show {slug} — view agent details

/edikt:agents show dba

Prints the full agent system prompt — domain identity, expertise, constraints.

suggest — get recommendations for your stack

/edikt:agents suggest

Recommended agents for your stack (go, chi):

  Already installed:
    architect
    backend
    dba
    qa

  Recommended (not installed):
    sre    — Reliability, observability, deployment
    api    — REST/GraphQL/gRPC contracts, versioning

How agents are chosen at init

When you run /edikt:init, edikt reads ~/.edikt/templates/agents/_registry.yaml and selects agents based on your detected stack:

• Always: architect, docs, qa
• Most projects: + sre, security, pm, api
• Go detected: + backend, dba
• TypeScript detected: + frontend, backend
• React/Vue/Angular/Svelte: + frontend, ux
• Next.js: + frontend, ux, seo
• Docker/K8s/Terraform: + platform
• Security keywords in project-context.md (payment, auth, HIPAA): + security
• Compliance keywords: + compliance

Customizing agents

This is /edikt:upgrade's behavior, not /edikt:agents's — documented here because it's what determines whether an edit you make to an installed agent survives the next upgrade. Two mechanisms prevent /edikt:upgrade from overwriting your changes:

File marker — add <!-- edikt:custom --> anywhere in the agent file:

---
name: dba
description: "..."
<!-- edikt:custom -->
tools:
  - Read
  - Grep
  - Glob
---

Config — list agents in .edikt/config.yaml:

agents:
  custom:
    - dba              # don't overwrite on upgrade
    - my-team-reviewer # not from edikt templates

Both are supported. Config takes precedence. Agents not in the edikt registry are always skipped by upgrade — they have no matching template to compare against.

Creating custom agents

Create a .md file in .claude/agents/:

---
name: my-domain-expert
description: "Reviews X for Y. Use proactively when Z files are modified."
tools:
  - Read
  - Grep
  - Glob
---

You are a {domain} specialist...

The description: field is what the model reads to decide when to delegate. Make it specific and include trigger conditions.

Natural language triggers

• "what agents do we have?" → /edikt:agents
• "add the performance agent" → /edikt:agents add performance
• "show me the dba agent" → /edikt:agents show dba
• "what agents are recommended for my stack?" → /edikt:agents suggest