retrospective

Extract and structure session domain knowledge into the four-layer CLAUDE storage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/swat9013/dotfiles --skill retrospective-swat9013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/swat9013/dotfiles/tree/main/.claude-global/skills/retrospective
Command: npx skills add https://github.com/swat9013/dotfiles --skill retrospective-swat9013

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The retrospective skill extracts domain knowledge from session conversations and persists it across a four-layer storage system to support long-term context and knowledge reuse.

Core Features & Use Cases

  • Extraction and structuring of project-specific knowledge from sessions
  • Categorization and consolidation across CLAUDE.md, rules/, skills/, and settings.local.json
  • Use case: After a project sprint, produce a consolidated context snapshot for onboarding and future references

Quick Start

Provide a session transcript to the retrospective skill to start extracting and persisting domain knowledge.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I persist session learnings as domain knowledge for future context?

To persist session learnings as domain knowledge, you provide a session transcript to extract and structure insights into a four-layer storage system across CLAUDE.md, rules/, skills/, and settings.local.json.

What is the best way to consolidate project knowledge after a sprint for onboarding?

The best way to consolidate project knowledge for onboarding is running a two-stage extraction process that categorizes session conversations into a persistent context snapshot for future reference.

Does the retrospective knowledge extraction require any specific dependencies?

Yes, knowledge extraction requires the jq dependency to process and structure session data into the storage layers for maintaining project-wide context.

How does session analysis handle duplicate or conflicting knowledge entries?

Session analysis handles duplicates and conflicts through robust error handling that ensures non-destructive updates, de-duplication, and conflict resolution when processing new versus cached data.

Can I use session analysis to update rules and settings without losing existing data?

Yes, session analysis performs non-destructive updates across CLAUDE.md, rules/, skills/, and settings.local.json, ensuring existing project knowledge remains intact while integrating new information.

What limitations exist when extracting domain knowledge from session conversations?

Limitations include dependency on jq for processing and the scope of extraction being limited to session conversation content, which requires complete transcripts to effectively capture and structure domain knowledge.