Phase 12b: Agent specialization configs — DevOps, Frontend-QA, Dev-QA, DevOps-QA #99

Closed
opened 2026-03-14 22:17:25 +00:00 by forgejo_admin · 0 comments
Contributor

Lineage

plan-pal-e-agency → Phase 12 (Agent Specialization) → Phase 12b (Agent configs)

Repo

forgejo_admin/claude-custom

User Story

As Betty Sue
I want domain-specialized agent configs deployed
So that I can spawn the right execution agent and the right QA expert for each domain

Context

Phase 12 splits the agent model into domain-specialized execution and expert QA agents. Phase 12a (completed) created the agent definition notes in pal-e-docs. This phase creates the actual runtime config files.

The agent model is evolving from 6 to 9 agents:

  • New execution agent: DevOps (split from Dev-Backend — Terraform/Salt/k8s/ArgoCD)
  • New QA agents: Frontend-QA, Dev-QA, DevOps-QA (replace generalist QA)
  • Narrowed: Dev-Backend loses IaC scope (Python/FastAPI only)
  • Deprecated: qa.md replaced by three domain-specific QA agents

Key design principle: execution agents are action-biased (hooks enforce SOP). QA agents are quality-biased (domain expertise + DORA process audit). See agent-devops, agent-frontend-qa, agent-dev-qa, agent-devops-qa notes in pal-e-docs for full specs.

File Targets

Files to create:

  • agents/devops.md — DevOps execution agent config (Terraform/Salt/k8s/ArgoCD/Helm, forgejo MCP, worktree isolation)
  • agents/frontend-qa.md — Frontend-QA expert reviewer (a11y, perf, responsive, UX, Impeccable compliance; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook)
  • agents/dev-qa.md — Dev-QA expert reviewer (PEP, OWASP, SQLAlchemy, test coverage, DORA process audit; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook)
  • agents/devops-qa.md — DevOps-QA expert reviewer (Terraform state, k8s security, ArgoCD, Salt, CNPG; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook)

Files to modify:

  • agents/dev-backend.md — Remove IaC from scope. Update description and constraints to Python/FastAPI/SQLAlchemy only. Add constraint: "Never write Terraform, Salt, or k8s manifests — that's DevOps's domain."
  • hooks/check-agent-spawn.sh — Add devops, frontend-qa, dev-qa, devops-qa to recognized agent types

Files to rename (NOT delete — keep for reference):

  • agents/qa.mdagents/qa.md.deprecated

Files NOT to touch:

  • agents/dev-frontend.md — already complete with Impeccable skills
  • agents/betty-sue.md — no changes needed
  • agents/dottie.md — no changes needed
  • hooks/block-write-tools.sh — already exists, QA agents reuse it

Acceptance Criteria

  • agents/devops.md exists with frontmatter: name, description, mcpServers (forgejo), isolation (worktree), model (inherit)
  • agents/frontend-qa.md exists with frontmatter: name, description, disallowedTools (Write,Edit,Bash), mcpServers (forgejo), model (inherit), PreToolUse hook (block-write-tools.sh)
  • agents/dev-qa.md exists with same QA frontmatter pattern as frontend-qa
  • agents/devops-qa.md exists with same QA frontmatter pattern as frontend-qa
  • agents/dev-backend.md updated: description mentions Python/FastAPI only, constraints exclude IaC
  • hooks/check-agent-spawn.sh recognizes all new agent types
  • agents/qa.md renamed to agents/qa.md.deprecated
  • Each agent config references its pal-e-docs profile note via mcp__pal-e-docs__get_note(slug="agent-{name}")

Test Expectations

  • Verify each new agent .md file has valid YAML frontmatter (no syntax errors)
  • Verify check-agent-spawn.sh accepts the new agent type names
  • Verify the deprecated qa.md no longer loads as an active agent

Constraints

  • Follow the exact pattern from agents/dev-frontend.md and agents/dev-backend.md for execution agents
  • Follow the exact pattern from agents/qa.md for QA agents (but with domain-specific content)
  • QA agents include DOMAIN REVIEW and PROCESS OBSERVATIONS sections in their review output template
  • Each agent .md body should tell the agent to read its full profile from pal-e-docs, not duplicate the full content
  • DevOps agent needs tofu constraints (not terraform), secrets pipeline awareness, tofu plan output in PR body
  • Use model: inherit not a specific model name

Checklist

  • PR opened
  • Tests pass
  • No unrelated changes

Closes: n/a (Betty Sue will close after merge + deploy verification)

  • plan-pal-e-agency — parent plan
  • phase-pal-e-agency-12-agent-specialization — phase note with full design principles
### Lineage `plan-pal-e-agency` → Phase 12 (Agent Specialization) → Phase 12b (Agent configs) ### Repo `forgejo_admin/claude-custom` ### User Story As Betty Sue I want domain-specialized agent configs deployed So that I can spawn the right execution agent and the right QA expert for each domain ### Context Phase 12 splits the agent model into domain-specialized execution and expert QA agents. Phase 12a (completed) created the agent definition notes in pal-e-docs. This phase creates the actual runtime config files. The agent model is evolving from 6 to 9 agents: - **New execution agent:** DevOps (split from Dev-Backend — Terraform/Salt/k8s/ArgoCD) - **New QA agents:** Frontend-QA, Dev-QA, DevOps-QA (replace generalist QA) - **Narrowed:** Dev-Backend loses IaC scope (Python/FastAPI only) - **Deprecated:** `qa.md` replaced by three domain-specific QA agents Key design principle: execution agents are action-biased (hooks enforce SOP). QA agents are quality-biased (domain expertise + DORA process audit). See `agent-devops`, `agent-frontend-qa`, `agent-dev-qa`, `agent-devops-qa` notes in pal-e-docs for full specs. ### File Targets Files to create: - `agents/devops.md` — DevOps execution agent config (Terraform/Salt/k8s/ArgoCD/Helm, forgejo MCP, worktree isolation) - `agents/frontend-qa.md` — Frontend-QA expert reviewer (a11y, perf, responsive, UX, Impeccable compliance; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook) - `agents/dev-qa.md` — Dev-QA expert reviewer (PEP, OWASP, SQLAlchemy, test coverage, DORA process audit; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook) - `agents/devops-qa.md` — DevOps-QA expert reviewer (Terraform state, k8s security, ArgoCD, Salt, CNPG; disallowedTools: Write,Edit,Bash; forgejo MCP; block-write-tools.sh hook) Files to modify: - `agents/dev-backend.md` — Remove IaC from scope. Update description and constraints to Python/FastAPI/SQLAlchemy only. Add constraint: "Never write Terraform, Salt, or k8s manifests — that's DevOps's domain." - `hooks/check-agent-spawn.sh` — Add `devops`, `frontend-qa`, `dev-qa`, `devops-qa` to recognized agent types Files to rename (NOT delete — keep for reference): - `agents/qa.md` → `agents/qa.md.deprecated` Files NOT to touch: - `agents/dev-frontend.md` — already complete with Impeccable skills - `agents/betty-sue.md` — no changes needed - `agents/dottie.md` — no changes needed - `hooks/block-write-tools.sh` — already exists, QA agents reuse it ### Acceptance Criteria - [ ] `agents/devops.md` exists with frontmatter: name, description, mcpServers (forgejo), isolation (worktree), model (inherit) - [ ] `agents/frontend-qa.md` exists with frontmatter: name, description, disallowedTools (Write,Edit,Bash), mcpServers (forgejo), model (inherit), PreToolUse hook (block-write-tools.sh) - [ ] `agents/dev-qa.md` exists with same QA frontmatter pattern as frontend-qa - [ ] `agents/devops-qa.md` exists with same QA frontmatter pattern as frontend-qa - [ ] `agents/dev-backend.md` updated: description mentions Python/FastAPI only, constraints exclude IaC - [ ] `hooks/check-agent-spawn.sh` recognizes all new agent types - [ ] `agents/qa.md` renamed to `agents/qa.md.deprecated` - [ ] Each agent config references its pal-e-docs profile note via `mcp__pal-e-docs__get_note(slug="agent-{name}")` ### Test Expectations - [ ] Verify each new agent .md file has valid YAML frontmatter (no syntax errors) - [ ] Verify check-agent-spawn.sh accepts the new agent type names - [ ] Verify the deprecated qa.md no longer loads as an active agent ### Constraints - Follow the exact pattern from `agents/dev-frontend.md` and `agents/dev-backend.md` for execution agents - Follow the exact pattern from `agents/qa.md` for QA agents (but with domain-specific content) - QA agents include DOMAIN REVIEW and PROCESS OBSERVATIONS sections in their review output template - Each agent .md body should tell the agent to read its full profile from pal-e-docs, not duplicate the full content - DevOps agent needs `tofu` constraints (not `terraform`), secrets pipeline awareness, tofu plan output in PR body - Use `model: inherit` not a specific model name ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes Closes: n/a (Betty Sue will close after merge + deploy verification) ### Related - `plan-pal-e-agency` — parent plan - `phase-pal-e-agency-12-agent-specialization` — phase note with full design principles
forgejo_admin 2026-03-14 22:40:05 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/claude-custom#99
No description provided.