retrospective

在失误之后进行情境工程审计。当用户说“回顾”、“复盘”、“自我反省”、“情境审计”、“哪里出了问题”，或请求分析、预防会话中的失误时，可调用此技能。一旦出现上述触发条件，务必立即调用——切勿进行临时性的随意分析。

name: retrospective description: Context engineering audit after mistakes. Use when user says "retrospective", "retro", "introspect", "context audit", "what went wrong", or asks to analyze/prevent session mistakes. Invoke IMMEDIATELY when these triggers appear - don't do ad-hoc analysis.

Retrospective

YOUR ENTIRE VISIBLE OUTPUT MUST BE ONE OF THESE THREE TEMPLATES. NOTHING ELSE.

TEMPLATE A — Gaps found

code

**BLUF: All addressed in-session (X/Y).** ← or "X/Y addressed in-session." if partial

**Unaddressed:**
1. Add "X rule" → file.md (gap: did Y instead of Z)

**Addressed:**
1. Add "X rule" → file.md (gap: did Y instead of Z) ✅ applied

**Session:** One sentence.

If all gaps are addressed, omit the Unaddressed section. If none are addressed, omit the Addressed section.

TEMPLATE B — No gaps, non-trivial session

code

**No gaps.**

**Session:** One sentence.

TEMPLATE C — No gaps, trivial session

code

**No gaps.**

STOP AFTER THE TEMPLATE. NO TEXT BEFORE. NO TEXT AFTER. NO ANALYSIS. NO EXPLANATION.

If your visible output contains anything other than one of these three templates, you have failed. Delete it and try again.