Agent skill
retrospect
Guided personal reflection that separates fact, interpretation, and emotion through structured inquiry. Use when "something feels off", "need to process this", "had a conflict", or decisions feel unclear. Not for technical decision analysis — use devils-advocate for that.
Install this agent skill to your Project
npx add-skill https://github.com/hairihou/dotfiles/tree/main/src/.config/claude/skills/retrospect
SKILL.md
Retrospect
Steps
- Listen: Understand the event
- Inquire: Ask 1-3 questions to separate Fact / Interpretation / Emotion
- Fact: "What exactly happened? What did you observe?"
- Interpretation: "What meaning did you assign to it? What assumptions are you making?"
- Emotion: "How did that make you feel? What was your gut reaction?"
- Deepen: Clarify facts, surface assumptions, acknowledge emotions
- Challenge interpretations: "Is there another way to read this situation?"
- Validate emotions: "That reaction makes sense given your interpretation."
- Integrate: Summarize and guide toward actionable next steps
- Separate what is known (fact) from what is inferred (interpretation)
- Propose 1-2 concrete actions based on facts, not interpretations
Guidelines
- Respond in user's language
- Facts and interpretations often blend; separate them gently
Start
$ARGUMENTS
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
hairihou/dotfiles
1on1-prep
Prepare for 1on1 meetings using a Psychological Safety x Responsibility framework. Use when preparing for a 1on1, noticing behavioral changes, or planning a difficult conversation with a report.
hairihou/dotfiles
bonsai
Maintain and groom config files in the current repository. Use when "bonsai", "tidy up", "prune configs", "clean up", "spring cleaning", or reviewing config health. Not for code quality review — use code-critic for that.
hairihou/dotfiles
npm-update-report
Dependency update workflow with vulnerability assessment and verification. Use when asked to check outdated packages, bump dependencies, run audit, do periodic dependency maintenance, or when security vulnerabilities are reported.
hairihou/dotfiles
session-insights
Analyze the current conversation for inefficiencies and improvement opportunities. Use when "how did this session go", "what went wrong", "what could I have done better", or reviewing session quality. Not for personal reflection — use retrospect. Not for logging work — use diary.
hairihou/dotfiles
pr
Create or update a GitHub pull request. Use when asked to create a PR, submit for review, or push changes as a PR. Not for code review comments — use conventional-comments for that.
hairihou/dotfiles
conventional-comments
Format code review comments using Conventional Comments labels and decorations. Use when writing inline review comments on a PR diff. Not for creating PRs — use pr for that. Not for complexity analysis — use code-critic for that.
Didn't find tool you were looking for?