reflect

Automate end-of-session reflections to update project observations and research notes.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/saross/personal-assistant --skill reflect-saross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/saross/personal-assistant/tree/main/skills/reflect
Command: npx skills add https://github.com/saross/personal-assistant --skill reflect-saross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session reflections help you rapidly capture project context, decisions, and observations after a session, keeping research logs up to date and aligned with priorities.

Core Features & Use Cases

  • Project-scoped reflections: Focused updates tied to the current working directory and project.
  • Priority-driven documentation: Updates follow a defined order in docs/notes/reflections/ to preserve sequence.
  • Audit-ready records: Entries include project name and session date for clarity and traceability.

Quick Start

Invoke the reflect command after a session to append structured reflections to the project’s docs/notes/reflections directory.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I automate end-of-session reflections for research logs?

You can automate end-of-session reflections by invoking a command that appends structured entries to your project's docs/notes/reflections directory. This preserves priority order and adds date-stamped entries to maintain research log traceability.

What is the best way to keep project notes and documentation traceable?

The best way to keep project notes traceable is to use structured guidance that enforces project scoping, date-stamped entries, and explicit project tagging. This ensures your documentation updates remain coherent and audit-ready.

Can I append session review entries to my current working directory directly?

Yes, you can append session review entries directly to your current working directory. The process updates the docs/notes/reflections folder within the active project, tying observations and updates to the specific project context.

Do I need to manually sort my documentation updates by priority?

No, you do not need to manually sort documentation updates by priority. The automated reflection process updates files following a defined order in the docs/notes/reflections directory to preserve the sequence automatically.

When do I need to use date-stamped entries for project observations?

You need to use date-stamped entries for project observations when building audit-ready research logs that require clear traceability. Structured date-stamping ensures each session review is tied to a specific timeline and project context.