retrospective

Name: retrospective
Availability: InStock
Author: floeorg

Review session interactions and propose updates to .claude/rules/ conventions.

7|Updated Mar 13, 2026

Search Tags:#claude #conversational-ai #rule-generation #session-review #ai-governance #policy-proposal

Ready to run

npx skills add https://github.com/floeorg/floe --skill retrospective-floeorg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/floeorg/floe/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/floeorg/floe --skill retrospective-floeorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review the session's interactions and propose additions or updates to .claude/rules/ conventions.

Core Features & Use Cases

Identifies points in the conversation that could become rules (recurring corrections, user feedback, implicit conventions, build/test failures, architectural decisions) and summarizes why they should become rules.
Cross-references proposed points with all existing .claude/rules/*.md to determine coverage, gaps, or necessary updates.
Presents concrete proposals one at a time, detailing type, target file, rationale, and specific changes; supports user decisions to Apply or Skip.
Produces a summary of changed files at the end of the session.

Quick Start

Review this session's interactions and propose patterns that should be added or updated in .claude/rules/.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I generate rules from a conversational AI session?▼

To generate rules from a conversational AI session, review the interactions to identify recurring corrections and architectural decisions, then propose additions or updates to .claude/rules/ conventions iteratively for user approval.

How does cross-referencing proposed rules with existing conventions work?▼

Cross-referencing proposed rules works by checking new proposals against all existing .claude/rules/*.md files to determine coverage gaps, identify necessary updates, and prevent redundant governance policies.

Can I audit session interactions to refine existing .claude rules?▼

Yes, you can audit session interactions to refine existing .claude rules by identifying user feedback and build failures, then presenting concrete updates one at a time for you to Apply or Skip.

What is the best way to coordinate inter-agent proposals during an AI governance workflow?▼

The best way to coordinate inter-agent proposals during an AI governance workflow is to implement a three-step process: identify rule-worthy points, cross-reference with existing rules, and present proposals iteratively for user approval.

What types of conversation points should become rules in a session review?▼

Points that should become rules in a session review include recurring corrections, implicit conventions, build or test failures, and architectural decisions that summarize why they need to be formalized.

Do I need existing .claude/rules/ files to propose convention updates?▼

You do not need existing .claude/rules/ files to propose convention updates, as the session review can identify gaps and establish new rules, then cross-reference them against any existing files to prevent duplication.