Side Quest 09-01f: Debugging Checklist

:dart: What You'll Do

You will apply a repeatable seven-step triage flow whenever a run produces unexpected output.

:clipboard: Before You Start

• Complete Side Quest: Diagnosing Common Agent Output Patterns

Checklist

1. Open the live log in Actions and scan for [error] lines first.
2. Check [plan] density. More than four consecutive plan lines without a tool call usually means your brief is underspecified.
3. Inspect [tool] and [result] lines to confirm expected data is returned.
4. Look for limit reached safe-output errors, such as E002: add-comment limit reached — 1 of 1 already used this run, and decide whether to increase max or tighten "post once" guidance.
5. Read the run summary and compare it to your expected write behavior.
6. Open the safe-output record in the job details and treat it as source of truth for writes.
7. If behavior is still unclear, ask the agentic-workflows skill to diagnose your workflow with a pasted snippet.

:white_check_mark: Checkpoint

• I can run this checklist in order without skipping steps
• I know where to find both live logs and safe-output records
• I can decide whether the root cause is prompt, data, permissions, or output limits
• I can gather a minimal log snippet to share for deeper diagnosis