audit-finding-triage

Classify and route agent halt-and-surface findings into resolution, deferral, escalation, or documentation buckets.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/lukeivers/loam --skill audit-finding-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-finding-triage
Source: https://github.com/lukeivers/loam/tree/main/plugins/dev-sdlc/skills/audit-finding-triage
Command: npx skills add https://github.com/lukeivers/loam --skill audit-finding-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of categorizing and routing halt-and-surface findings returned by dispatched agents, reducing manual effort and improving response consistency.

Core Features & Use Cases

  • Automated Triage: Reads agent return artifacts and status files to classify findings into predefined buckets.
  • Decision Consistency: Applies operational criteria to determine whether findings should be resolved immediately, deferred, escalated, or captured for future review.
  • Use Case: When an agent reports a violation or ambiguity, this Skill helps quickly assign the finding to the correct action path and ensures proper documentation.

Quick Start

Use the audit-finding-triage skill to process the latest agent findings and route them accordingly.

Frequently Asked Questions about audit-finding-triage

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

FAQPage Schema
How do I automate the triage of agent findings from operational workflows?

Automating agent finding triage involves reading return artifacts and classifying issues into predefined buckets like resolution, deferral, or escalation. This ensures consistent handling of halt-and-surface findings without manual effort.

What is the best way to classify and route halt-and-surface findings from AI agents?

The best way to classify halt-and-surface findings is applying standard triage rules to agent return artifacts. This separates issues into multi-bucket decision criteria for immediate resolution, escalation, or documentation.

How do I route operational violations reported by AI agents for faster resolution?

Routing reported violations requires applying operational criteria to agent status files to determine the correct action path. This directs findings to resolution, deferral, escalation, or documentation for accountability.

Can I use automated triage to handle complex multi-bucket decision criteria for agent findings?

Yes, automated triage supports complex multi-bucket decision criteria by applying standard operational rules. It evaluates agent findings and routes them across resolution, deferral, escalation, or documentation paths.

What are the limitations of automating agent finding classification and routing?

Automated agent finding classification relies on predefined operational rules and return artifacts. It may not effectively route novel ambiguities outside standard triage criteria without manual review or updated decision logic.