C.W.K.
Stream
Lesson 03 of 05 · published

Reflection and Verification

~28 min · verification, reflection

Level 0Observer
0 XP0/40 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

The first answer is a draft

Reflection is not mystical self-awareness. It is a review pass. The agent compares its output against requirements, finds gaps, and either fixes them or reports residual risk.

The most reliable verification is tool-based: tests, linters, schema checks, database queries, diff inspection. Use the model to reason about quality, but use tools to verify facts whenever possible.

Separate generator and reviewer roles

Even in one model call, use separate instructions for generation and review. For higher risk, use a different model, a deterministic checker, or a human.

Do not let reflection become infinite polishing. Set a maximum number of review cycles and clear acceptance criteria.

Code

Reflection pass·text
Review the result against the original requirements.
Return:
- APPROVED if complete
- ISSUES with exact missing or incorrect parts
- RISK if unverifiable without external checks
Do not suggest cosmetic changes unless they affect the requirement.

External links

Exercise

Create a reviewer prompt for one agent output you care about. Include what counts as APPROVED.
Hint
Approval criteria should be objective enough to stop.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.