| name | retrospective |
| description | Session retrospective: review what was done, identify reusable patterns worth turning into skills. Use at the end of a session to extract learnings and skill candidates. Triggers: "振り返り", "retrospective", "retro", "セッション振り返り", "スキル化できるものある?", "今日の振り返り".
|
Retrospective Skill
Analyze the current session to extract reusable patterns, recurring workflows, and skill candidates.
Workflow
1. Session Summary
Review the conversation history and summarize:
- What was done: features implemented, bugs fixed, tasks completed
- What tools/commands were used repeatedly
- What friction occurred: errors, retries, misunderstandings, manual steps
2. Pattern Detection
Look for these signals that indicate a workflow should become a skill:
Repetition signals:
- Same sequence of commands executed 2+ times in this session
- A workflow that was also done in previous sessions (check MEMORY.md)
- Manual steps that could be automated (e.g., "start server, then check proxy, then curl endpoint")
Friction signals:
- Steps where Claude had to retry or the user had to correct
- Configuration that was forgotten and had to be redone
- Verification steps that were skipped and caused issues later
Complexity signals:
- Multi-step workflows with a specific order (build → test → deploy)
- Domain-specific knowledge needed (project conventions, API patterns)
- Checklists that need to be followed consistently
3. Evaluate Candidates
For each candidate pattern, assess:
