tslateman/retro
skills/retro/SKILL.md
Reflect on recent work—capture learnings and surface what to think about next
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add tslateman/duet retroInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 6:25 PM9.2s1 file scanned
SKILL.md
- name:
- retro
- description:
- Reflect on recent work—capture learnings and surface what to think about next
Session Retrospective
Overview
Reflect on the work just completed in this conversation. Extract insights, not summaries.
What I Learned
Identify 2-4 concrete technical insights from this session:
- Patterns discovered or reinforced
- Gotchas or surprises encountered
- Techniques that worked well (or didn't)
- Connections to other parts of the codebase
Focus on insights, not a summary of actions taken.
What to Think About Next
Surface 2-4 open threads worth considering:
- Unfinished work or TODOs
- Edge cases or risks not yet addressed
- Potential improvements or refactors
- Questions that came up but weren't resolved
Be specific—name files, functions, or concepts rather than speaking abstractly.
Memory Health Check
Before asking about persistence, check the current project's MEMORY.md:
- Read the file from the project's auto memory directory
- Count lines -- if over 50, note the size
- Scan for staleness signals:
- Items containing "resolved", "fixed", "done", "completed"
- Date references from more than 30 days ago
- Sections that duplicate CLAUDE.md headers
- Report briefly: "MEMORY.md: [N] lines, [issues found or 'healthy']"
If issues are found, include them in the question to the user -- e.g., "MEMORY.md has 3 stale items. Want to prune them while persisting new insights?"
After generating the retro, ask the user if any insights are worth persisting to auto memory. Use AskUserQuestion with options like "Yes, update MEMORY.md", "Yes, and prune stale items", and "No, just this session".
If yes, read the current MEMORY.md from the project's auto memory directory and intelligently merge the new insights—don't duplicate existing points, add new ones under the appropriate sections.
Related Skills
tslateman/vibe-check
development
VerifiedTrustedCommunity
Judgment linter for vibe-coded output — reads the energy of the code, not just correctness. Use when the user says "vibe check", "check this vibe code", "does this hold up", "sanity check this AI code", or after a fast generation session before committing.
SKILL.mdUpdated Apr 25, 2026
tslateman/vamp
tools
VerifiedTrustedCommunity
Survey the project and choose what to play next
SKILL.mdUpdated Apr 25, 2026
tslateman/testing
development
VerifiedTrustedCommunity
Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.
SKILL.mdUpdated Apr 25, 2026
tslateman/sweep
testing
VerifiedTrustedCommunity
Post-op check for artifacts, damage, and stale references after agent work
SKILL.mdUpdated Apr 25, 2026