agent-introspection-debugging

原文涵盖的主题

• Agent Introspection Debugging
• When to Activate
• Scope Boundaries
• Four-Phase Loop
• Phase 1: Failure Capture
• Phase 2: Root-Cause Diagnosis
• Phase 3: Contained Recovery
• Phase 4: Introspection Report

Use this skill when an agent run is failing repeatedly, consuming tokens without progress, looping on the same tools, or drifting away from the intended task. This is a workflow skill, not a hidden runtime. It teaches the agent to debug itself systematically before escalating to a human. Maximum tool call / loop-limit failures Repeated retries with no forward progress Context growth or prompt drift that starts degrading output quality File-system or environment state mismatch between expectation and reality Tool failures that are likely recoverable with diagnosis and a smaller corrective action Activate this skill for: capturing failure state before retrying blindly diagnosing common agent-specific failure patterns applying contained recovery actions producing a structured human-readable debug report Do not use this skill as the primary source for: feature verification after code changes; use verification-loop framework-specific debugging when a narrower ECC skill already exists runtime promises the current harness cannot enforce automatically Before trying to recover, record the failure precisely. Capture: error type, message, and stack trace when available last meaningful tool ca

这里只展示节选，请以完整原文和当前要求为准。