reflect

Summarize session tasks, decisions, and open issues into recall history files.

108|10|Updated Dec 29, 2024
One-click install
npx skills add https://github.com/Qredence/agentic-fleet --skill reflect-qredence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/Qredence/agentic-fleet/tree/main/.fleet/context/system/reflect
Command: npx skills add https://github.com/Qredence/agentic-fleet --skill reflect-qredence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain continuity across sessions by consolidating learnings into a centralized recall history, reducing context loss and the need to re-derive decisions.

Core Features & Use Cases

  • Summarize Session: Generate a concise recap of tasks completed, key decisions, and open issues.
  • Archive to Recall History: Append the summary to recall/history.md or timestamped files in recall/sessions.
  • Reset Scratchpad: Clear the current recall scratchpad to prepare for the next task.

Use Case: At the end of a long planning session, run reflect to preserve decisions and move on with a clean scratchpad for the next task.

Quick Start

Run the reflect skill to read .fleet/context/recall/current.md, summarize tasks and decisions, append the summary to recall/history.md, and clear .fleet/context/recall/current.md for the next task.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I consolidate session learnings into a recall history?

To consolidate session learnings into a recall history, run the reflect skill to read your current recall file, summarize completed tasks and decisions, and append the summary to history.md before clearing the scratchpad.

What is the best way to archive session summaries and reset a scratchpad?

Archiving session summaries and resetting a scratchpad involves reading the current session data, generating a concise recap of tasks and open issues, archiving it to recall/sessions, and clearing the current.md scratchpad file.

When do I need to archive session context for knowledge management?

You need to archive session context for knowledge management at the end of a long working session to preserve key decisions and open issues, reducing context loss and preventing the need to re-derive decisions later.

Does the reflect skill require any dependencies to summarize tasks?

No, the reflect skill requires no dependencies to summarize tasks. It directly reads .fleet/context/recall/current.md, updates the history files, and resets the scratchpad without external components.

How does recall archiving handle open issues from a previous task?

Recall archiving handles open issues by explicitly summarizing them from the current session data and appending them to timestamped files in recall/sessions or the central history.md file for future reference.