reflect

Document session lessons and patterns into Serena memory records.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill reflect-gudzenkov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/reflect
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill reflect-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document and preserve insights from a session to guide future work and learning.

Core Features & Use Cases

  • Session documentation: capture lessons learned and notable outcomes.
  • Pattern identification: detect recurring approaches and improvements.
  • Blocker tracking: note blockers and resolutions for future avoidance.
  • Cross-session learning: enable knowledge transfer across projects.

Quick Start

Summarize this session and save a reflection record to Serena memory.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture session learnings for future project improvement?

Capture session learnings by documenting lessons, blockers, and optimization opportunities in structured records. This enables pattern identification and cross-session knowledge transfer to guide future work.

What is a post-session reflection record and when do I need it?

A post-session reflection record documents notable outcomes and recurring approaches from completed work. You need it during post-session reviews to preserve insights and support meta-improvement across projects.

How do I save a session review to Serena memory?

Save a session review to Serena memory by summarizing the session and storing it under the reflect/ directory. Records require fields including date, session_id, project, duration_estimate, and completion status.

Can I track recurring blockers and resolutions across multiple projects?

Track recurring blockers and resolutions across multiple projects by documenting them in reflection records. This cross-project learning approach notes blockers and their resolutions for future avoidance.

What fields are required when documenting a session for cross-project learning?

Documenting a session for cross-project learning requires fields including date, session_id, project, duration_estimate, and completion. These structured fields enable pattern identification and knowledge transfer.

Does this approach work for identifying patterns in session documentation?

Identifying patterns in session documentation works by recording lessons learned and notable outcomes consistently. This enables detection of recurring approaches and improvement opportunities across sessions.