failure-review.md

Failure Review

Field	Value
Task ID	ADD-XXXX
Iteration	Rn (e.g., R1, R2, R3)
Date	YYYY-MM-DD
Reviewer

---

Failure Description

What went wrong? Be specific and factual.

Root Cause Phase

Which ADD phase is the primary source of this failure?

• SCOPE — Task was too broad, ambiguous, or poorly defined.
• FRAME — Context was incomplete, noisy, or contradictory.
• CONSTRAIN — Constraints were vague, missing, or conflicting.
• EXECUTE — Agent underperformed despite adequate preparation.

Root Cause Detail

Why did that phase fail? Be specific.

Factor	Assessment
Was the intent clear?	Yes / No —
Were non-goals listed?	Yes / No —
Was context complete?	Yes / No —
Was context curated (no noise)?	Yes / No —
Were constraints testable?	Yes / No —
Were forbidden actions listed?	Yes / No —
Was the prompt well-composed?	Yes / No —

What the Agent Did Wrong

Describe the specific failure in the agent's output.

What the Process Did Wrong

Describe what the human could have done differently in preparation.

Correction Plan

Specific changes to make before the next iteration.

Phase to Revisit	Change
SCOPE / FRAME / CONSTRAIN	[Specific change]

Re-entry Point

After applying the correction, re-enter the ADD cycle at:

• SCOPE (intent needs revision)
• FRAME (context needs updating)
• CONSTRAIN (constraints need tightening)
• EXECUTE (re-run with updated artifacts)

Pattern Detection

Is this a recurring failure type?

• First occurrence
• Recurring — seen in tasks: [list Task IDs]

If recurring, should this become:

• A new default constraint in templates
• An anti-pattern entry
• A project-specific rule
• A context pack default inclusion

Notes

Additional observations.