skills.rest
Heavy-Chain-Engineering
Heavy-Chain-EngineeringOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retrospective

Summarize development sessions into structured lessons for LESSONS.md and CLAUDE.md.

8|1|Updated Feb 13, 2026
Search Tags:#architecture#playbook#learning#retrospective#principles#software-engineering
One-click install
npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill retrospective-heavy-chain-engineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Heavy-Chain-Engineering/etc/tree/main/skills/retrospective
Command: npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill retrospective-heavy-chain-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a personal engineering coach, converting development sessions into structured learning that highlights workflow improvements, missed or applied software principles, and architectural insights to build a durable playbook over time.

Core Features & Use Cases

  • Analyze sessions to extract actionable workflow improvements and identify engineering principles demonstrated or missed.
  • Surface architectural insights and compile them into a reusable personal playbook that grows with each project.
  • Provide a repeatable retrospective workflow including LESSONS.md and CLAUDE.md integration for ongoing learning.

Quick Start

Invoke a retrospective on this session to generate a structured summary and entry for your engineering playbook.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I turn a development session into a structured engineering playbook?▼

You can capture architectural insights by reviewing cross-project patterns and evaluating applied or missed software engineering principles. This identifies durable workflow improvements and compiles them into a reusable personal engineering playbook.

What is the best way to track missed software engineering principles during a project?▼

Tracking missed software engineering principles involves running a retrospective on your development session to identify gaps in your approach. It surfaces these missed concepts and queues them as actionable lessons and study items for ongoing learning.

How do I document cross-project patterns for long-term software architecture learning?▼

Document cross-project patterns by summarizing development sessions to surface recurring architectural insights. Compiling these insights into a personal playbook creates a durable reference that grows with each project and informs future architecture decisions.

Can I integrate development session lessons into LESSONS.md and CLAUDE.md files?▼

You can integrate session lessons into LESSONS.md and CLAUDE.md files by generating structured retrospective outputs. This workflow provides actionable lessons and playbook updates formatted specifically for seamless integration into these documentation files.

Does a retrospective workflow help identify actionable workflow improvements for software engineering?▼

A retrospective workflow helps identify actionable workflow improvements by systematically analyzing your development sessions. It extracts specific process bottlenecks and architectural insights, converting them into a structured engineering playbook for continuous improvement.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
yebotyebot
9

learning-taxonomy

Categorize session learnings into taxonomy types and route them to memory files.

Community
Advanced
elwa2elwa2

architecture_guardian

Analyze software project structures for scalable architecture design.

Community
Advanced
bdbchbdbch
2

code-review

Automate code commit reviews for bugs and SOLID principle adherence.

Community
Advanced