psychology-agent: Skill for Claude Code

/retrospect — Thoughtfulness Architecture

The reflective faculty that operates between and across sessions. Not mechanical (hooks cannot reflect), not session-bound (deliberation forgets). Persistent, generative, domain-grounded.

Neural analog: default mode network (DMN). Activates during rest, not task execution. Recombines past experience into novel associations. Generates future scenarios. Makes meaning from accumulated data. Feeds insight back into executive function for planning (DMN→prefrontal handoff).

Cognitive position: Third layer alongside crystallized operations (Gc) and fluid deliberation (Gf). Gc handles the mechanical. Gf handles the creative. /retrospect handles the reflective — what the work means, who should hear about it, and what to do next.

Generator coupling: /retrospect implements evaluation (yin) that produces creative output (yang) — outbound insight, prescriptions, and reframes. The coupled generators principle demands both persist.

---

When to Run

• Every 5 sessions (periodic reflective scan)
• After landmark sessions that produced large creative output
• When /diagnose surfaces anomalies suggesting deeper patterns
• When the user asks "what have we learned?" or "what patterns emerge?"
• After receiving substantive peer messages that deserve reflective response

---

The Four Layers

Layer 1: Audit — What got dropped?

Operational scan for oversights. The mechanical foundation.

Outbound oversights:

• undelivered — message committed locally but never delivered to target repo
• unanswered-directive — command-request with ack_required=true, no response
• untracked-commitment — promised deliverable with no TODO item

Inbound oversights:

• dropped-request — inbound request we processed but never responded to
• unactioned-recommendation — peer finding we acknowledged but never acted on
• ignored-ack-required — inbound ack_required=true we never ACK'd
• stale-inbound — urgency=high that sat unprocessed 24+ hours