reflect

Capture session learnings into categorized memory files within .claude/memory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically capture and organize key learnings, decisions, and patterns from your work sessions, preventing valuable insights from being lost.

Core Features & Use Cases

  • Session Retrospective: Facilitates a structured review of what was accomplished, what went well, and what could be improved.
  • Knowledge Capture: Organizes insights into categorized memory files (Architecture, Debugging, Preferences, Decisions).
  • Use Case: After a complex debugging session, use /reflect to quickly document the specific workaround you discovered and categorize it under 'Debugging' for future reference.

Quick Start

Use the reflect skill to review this session and update memory files.

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 and decisions for future reference?

You can capture session learnings by documenting insights into organized memory files within the .claude/memory directory. This requires categorizing knowledge into predefined topics like Architecture, Debugging, Preferences, and Decisions to maintain a stable knowledge state.

What is the best way to run a session retrospective for software engineering tasks?

Running a session retrospective involves facilitating a structured review of what was accomplished, what went well, and what could be improved. This process extracts key learnings and patterns, organizing them into categorized memory files for immediate knowledge capture.

How does knowledge capture into memory files actually work?

Knowledge capture works by writing specific insights and workarounds discovered during a session into categorized memory files. These files are stored within the .claude/memory directory and must be sorted into predefined topics to keep the current state of knowledge stable and organized.

Can I use this approach to document a complex debugging workaround?

Yes, you can document a complex debugging workaround by using a retrospective command to immediately capture the specific insight. You then categorize it under the 'Debugging' topic within your memory files for future reference.

Do I need to manually categorize insights when logging session memory?

Yes, categorizing insights into predefined topics like Architecture, Debugging, Preferences, and Decisions is required. This strict categorization maintains a stable, current state of knowledge within the memory directory structure.