drn/retro
agents/skills/retro/SKILL.md
Run a structured retrospective or post-incident review with optional knowledge base capture. Use for running retrospectives, postmortems, or incident reviews.
$ install --global
skillsauthnpx skillsauth add drn/dots 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 21, 2026, 10:57 AM50.1s1 file scanned
SKILL.md
- name:
- retro
- description:
- Run a structured retrospective or post-incident review with optional knowledge base capture. Use for running retrospectives, postmortems, or incident reviews.
Retrospective
Structured retrospective for projects, sprints, or incidents. Captures learnings and optionally persists them to the knowledge base.
Arguments
$ARGUMENTS- Optional:--incidentfor post-incident template, or a topic/project name
Context
- Recent commits: !
git log --oneline -20 2>/dev/null | head -20 - Merged PRs: !
gh pr list --state merged --limit 10 2>/dev/null | head -10 - Knowledge base: !
cat context/knowledge/index.md 2>/dev/null | head -30 - Current branch: !
git branch --show-current
Instructions
Step 1: Choose template
IF --incident is in $ARGUMENTS, use the Incident template.
OTHERWISE, use the Standard template.
Step 2: Gather context
Review the recent commits and merged PRs from the context above. Summarize the scope of work that this retro covers. If the user provided a topic, focus on that.
Step 3: Present and collaborate
Standard Template
## Retrospective: <topic or date>
### What Went Well
- <positive outcomes, wins, good patterns>
### What Did Not Go Well
- <pain points, friction, mistakes>
### Action Items
- [ ] <concrete next step with owner if applicable>
### Key Learnings
- <insights to carry forward>
Incident Template
## Post-Incident Review: <incident name>
### Timeline
| Time | Event |
|------|-------|
| | <what happened> |
### Impact
- **Users affected:**
- **Duration:**
- **Severity:**
### Root Cause
<what actually caused the issue>
### What Went Well
- <effective response actions>
### What Did Not Go Well
- <gaps in detection, response, or prevention>
### Action Items
- [ ] <concrete remediation with owner and deadline>
### Follow-ups
- [ ] <longer-term improvements>
Present the template pre-filled with whatever you can infer from the git context. Ask the user to fill in, correct, or expand each section. Iterate until the user is satisfied.
Step 4: Knowledge capture (optional)
IF a knowledge base exists (check context above for context/knowledge/index.md):
- Propose adding key learnings as a new topic or updating an existing topic
- Only add durable, reusable insights — not session-specific details
- Follow the format in
/knowledge(bold entity names, standalone facts, date-stamp volatile info)
IF no knowledge base exists, skip this step entirely. Do not suggest creating one.
Step 5: Save
Offer to:
- Copy to clipboard
- Save to
.context/retros/<date>-<slug>.md - Both
Related Skills
drn/address-comments
development
VerifiedTrustedCommunity
Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
23SKILL.mdUpdated May 16, 2026
drn/rereview-loop
tools
VerifiedTrustedCommunity
Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-visual-explainer
development
VerifiedTrustedCommunity
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-setup-goal
development
VerifiedTrustedCommunity
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
23SKILL.mdUpdated May 13, 2026