rrr

Generate a session retrospective markdown document with AI Diary and Honest Feedback sections.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ContentsUS/Agentic-AI-Paji --skill rrr-contentsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rrr
Source: https://github.com/ContentsUS/Agentic-AI-Paji/tree/main/.claude/skills/rrr
Command: npx skills add https://github.com/ContentsUS/Agentic-AI-Paji --skill rrr-contentsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill captures the essence of a work session, documenting activities, learnings, and outcomes to foster continuous improvement and provide valuable context for future tasks.

Core Features & Use Cases

  • Session Retrospective Creation: Generates a detailed markdown document summarizing the session.
  • AI Diary: Captures first-person narrative of the AI's thought process, challenges, and decisions.
  • Honest Feedback: Provides a frank assessment of session effectiveness, tools, and process.
  • Use Case: After completing a complex bug fix, use rrr to document the problem, the steps taken, the lessons learned, and any suggestions for improving the debugging process.

Quick Start

Create a retrospective for the current session.

Frequently Asked Questions about rrr

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

FAQPage Schema
How do I generate a session retrospective for continuous improvement?

A session retrospective is generated by gathering Git logs, branch status, and timestamps to produce a detailed markdown document capturing activities, learnings, and outcomes for future reference.

What is an AI diary and how does it document a work session?

An AI diary is a first-person narrative of the AI's thought process, challenges, and decisions captured during a work session. It provides valuable context for continuous improvement and future tasks.

How do I document a bug fix to capture lessons learned and process feedback?

Document a bug fix by generating a retrospective report that captures the problem, steps taken, lessons learned, and honest feedback. This provides frank assessment of session effectiveness and process.

Do I need Git logs and branch status to create a session summary?

Yes, Git logs, branch status, and timestamps are required to create a comprehensive session summary. These inputs allow the retrospective to accurately capture session activities and outcomes.

Can I get honest feedback on my debugging process and tools used?

Honest feedback on your debugging process is generated as part of the session retrospective document. It provides a frank assessment of session effectiveness, tools, and process for continuous improvement.

What's the best way to maintain an AI diary for software engineering sessions?

The best way to maintain an AI diary is to generate a detailed session retrospective after completing complex tasks. This captures the AI's narrative, decisions, and challenges for future reference.