kata-agent-feedback-design

Design agent feedback loops with metrics, SLOs, and alert runbooks.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-agent-feedback-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-agent-feedback-design
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-agent-feedback-design
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-agent-feedback-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineering teams define a reliable agent feedback loop by specifying concrete feedback modalities, objective metrics, and production SLOs that guide continuous improvement.

Core Features & Use Cases

  • Feedback loop blueprint for agents: Specifies HITL (human confirmation) for irreversible actions and optional critic review to gate quality before actions proceed.
  • Objective metrics and learning-closure: Enforces at least three operational metrics with canonical names, runtime measurement rules, thresholds, windows, and remedial actions on deviation.
  • Tier-1/2 production readiness: Requires SLOs with explicit SLI, objectives, error-budget policy, and alert runbooks so failures trigger actionable operational response.

Example use case: define how an agent that drafts and submits business operations outputs will be monitored for availability, p99 latency, and quality signals, including what to do when thresholds are breached.

Quick Start

Ask an AI to generate feedback.md and metrics.md for a tier-1 agent named {agent} with at least three metrics, complete SLO YAML, and runbooks for each critical alert.

Frequently Asked Questions about kata-agent-feedback-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an agent feedback loop for production LLM agents?

Designing an agent feedback loop requires specifying HITL gating for irreversible actions, critic-based quality review, and objective metrics to measure and remediate production behavior. This generates a structured feedback blueprint for continuous operational learning.

What SLOs do I need for tier-1 production agents?

Tier-1 production agents require SLOs with explicit SLI definitions, error-budget policies, and alert runbooks. You must define tier-1 or tier-2 SLO YAML configurations ensuring every critical alert triggers an actionable operational response for metric-driven degradation states.

How do I define operational metrics for monitoring agent quality?

Operational metrics for agent monitoring require at least three objective metrics with canonical names, runtime measurement rules, thresholds, and windows. You must provide runtime operational definitions and remedial actions to execute when metric deviations occur across agent turns.

When do I need human-in-the-loop gating for LLM agents?

Human-in-the-loop gating is needed for irreversible actions executed by production agents. You define HITL confirmation modalities alongside optional LLM critic reviews to gate quality before actions proceed, ensuring safe remediation for tier-1 or tier-2 operational deployments.

Can I generate runbooks for critical agent alerts automatically?

Generating runbooks for critical agent alerts is a core requirement of production readiness. You must ensure every critical alert defined in your SLO YAML has a corresponding runbook, specifying actionable operational responses for per-alert remediation across agent turns.