Facilitates structured task retrospectives to extract actionable lessons.
Install
mkdir -p .claude/skills/retro-lowyshin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17558" && unzip -o skill.zip -d .claude/skills/retro-lowyshin && rm skill.zipInstalls to .claude/skills/retro-lowyshin
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Post-task retrospective and learning extraction skill. Inspired by gstack's /retro and integrated with K-Layer. Use this after completing a significant task or resolving a complex issue to document lessons learned and improve future performance. Triggers: retro, retrospective, post-mortem, lessons learned, 회고, 사후 분석, 振り返りKey capabilities
- →Summarize completed tasks
- →Identify successful aspects of implementation
- →List pain points, bottlenecks, or mistakes
- →Extract actionable advice for future tasks
- →Integrate lessons into the Knowledge Layer as source-linked claims
How it works
The skill guides a structured reflection process after a task is completed. It prompts for successes, challenges, and lessons learned, then converts these lessons into K-Layer claims.
Inputs & outputs
When to use retro
- →Running a post-mortem
- →Documenting lessons learned
- →Improving future project performance
About this skill
Retro Skill
The retro skill helps you reflect on a completed task to extract valuable insights and prevent future mistakes.
Workflow
- Summary: Briefly summarize the completed task.
- What went well: List the successful aspects of the implementation.
- What could be improved: Identify pain points, bottlenecks, or mistakes.
- Lessons Learned: Extract actionable advice for future tasks.
- K-Layer Integration: Automatically convert lessons into "Source-linked claims" for the Knowledge Layer.
Usage
/retro [task-id or feature-name]
Template
The retrospective should follow this structure:
📝 Task Retrospective: [Feature Name]
- Completion Date: YYYY-MM-DD
- Related Task/Issue: [Link]
🚀 Successes
- [Item 1]
- [Item 2]
⚠️ Challenges & Mistakes
- [Problem 1]: [Root Cause]
- [Problem 2]: [Root Cause]
💡 Key Lessons
- [Lesson 1] -> [Action for next time]
- [Lesson 2] -> [Action for next time]
🧠 K-Layer Claims
- [Claim 1]: [Source Reference]
- [Claim 2]: [Source Reference]
When not to use it
- →Before completing a significant task
- →For tasks that did not involve complex issues
- →For general project management without a retrospective focus
Limitations
- →Only applicable after a significant task is completed
- →Requires a task-id or feature-name as input
- →Focuses on documentation, not direct problem-solving
How it compares
This skill provides a specific template and workflow for post-task retrospectives, ensuring consistent documentation of lessons learned and integration with a knowledge base, unlike informal feedback.
Compared to similar skills
retro side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| retro (this skill) | 0 | 2mo | Review | Beginner |
| session-handoff | 13 | 2mo | Review | Beginner |
| spec-to-backlog | 8 | 3mo | No flags | Intermediate |
| create-handoff | 3 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by LowyShin
View all by LowyShin →You might also like
session-handoff
davila7
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
create-handoff
parcadei
Create handoff document for transferring work to another session
moai-workflow-project
modu-ai
Integrated project management system with documentation, language initialization, and template optimization modules. Use when setting up projects, generating documentation, configuring multilingual support, or optimizing templates.
granola-core-workflow-b
jeremylongshore
Post-meeting note processing and sharing workflow with Granola. Use when reviewing meeting notes, sharing with team members, or processing action items after meetings. Trigger with phrases like "granola post meeting", "share granola notes", "granola follow up", "process meeting notes", "granola action items".
reporting
comeredon
Final pipeline execution report format. Defines the structure, agent registry, Mermaid gantt chart, and change summary. Used by AnalystAgent in Phase 6.