skills.rest
zcaceres
zcaceresCOMMUNITY
Explore all skills by this author →
Website𝕏@zachcaceresGitHub

reflect-on-conversation

Analyzes conversation history to produce a structured retrospective on prompting, performance, and workflow efficiency.

7|Updated May 28, 2026
Search Tags:#productivity#retrospective#meta-analysis#prompt-engineering#workflow-optimization#agent-performance
One-click install
npx skills add https://github.com/zcaceres/skills --skill reflect-on-conversation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect-on-conversation
Source: https://github.com/zcaceres/skills/tree/main/skills/reflect-on-conversation
Command: npx skills add https://github.com/zcaceres/skills --skill reflect-on-conversation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of structured feedback in AI-assisted workflows, helping users and agents identify inefficiencies, communication gaps, and missed opportunities for automation.

Core Features & Use Cases

  • Structured Retrospective: Generates a comprehensive analysis of prompting, agent performance, and system gaps.
  • Actionable Improvement: Provides prioritized lists of new tools to build, prompting strategies to adopt, and documentation updates.
  • Use Case: After a complex debugging session, run this skill to identify why the agent diverged into a rabbit hole and generate a checklist to prevent similar issues in future tasks.

Quick Start

Run the reflect-on-conversation skill to analyze our current session and provide a retrospective report.

Frequently Asked Questions about reflect-on-conversation

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

FAQPage Schema
How do I analyze an AI conversation history to improve my prompt engineering?▼

To analyze conversation history, you can generate a structured retrospective that evaluates user prompting, agent performance, and workflow efficiency to identify communication gaps and actionable improvements. This process highlights opportunities to refine your prompt engineering strategies.

What is the best way to identify workflow inefficiencies after a complex debugging session?▼

Identifying workflow inefficiencies involves reviewing the full conversation context to evaluate reasoning quality and tool usage. A structured retrospective can pinpoint why an agent diverged into rabbit holes and generate a checklist to prevent similar technical debt in future tasks.

Can I use a retrospective meta-analysis to find opportunities for custom tool development?▼

A retrospective meta-analysis can identify missed opportunities for automation and system gaps. By analyzing past sessions, it provides a prioritized list of new custom tools to build, helping you optimize future agent performance and development workflows.

How do I evaluate agent performance and adherence to project rules during software engineering tasks?▼

Evaluating agent performance requires access to the full conversation context to assess reasoning quality, tool usage, and adherence to project rules. A structured retrospective analyzes these factors to expose technical debt and documentation gaps within software engineering tasks.

Does generating a conversation retrospective require any specific dependencies or external libraries?▼

Generating a conversation retrospective does not require external dependencies or libraries. The analysis operates directly on the available conversation context to evaluate reasoning quality and workflow efficiency without needing additional setup.

Related Skills

Explore More Software Engineering Skills→
arroyo2009jose-maxarroyo2009jose-max

primer

Load project context from BUSINESS_LOGIC.md, features, database, and configuration.

Community
Intermediate
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
Tonybleything76Tonybleything76

cto-advisor

Provide strategic guidance and tools for CTOs to manage technical debt and scale teams.

Community
Advanced
ReidondReidond

session-retrospective

Analyze Claude Code session history to identify recurring agent behavior problems.

Community
Advanced