Project Retrospective
Turn a completed or paused body of work into an evidence-based retrospective covering goals, outcomes, decisions, pivots, effective practices, friction, failed approaches, unfinished work, open questions, and concrete improvements. Use with conversation history, project trackers, session notes, plans, logs, or user-specified files and folders across engineering, research, writing, automation, and…
Install
$ agentstack add skill-batteryshark-skill-tap-project-retrospective ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Project retrospective
Extract lessons from what happened without turning the result into blame, self-congratulation, or a transcript.
Inputs
Use the current conversation and any sources the user explicitly places in scope. For files or folders, run bin/project-retrospective SOURCE... to inventory supported text and --emit only when the collected content is appropriate to place in the current context.
Do not search private session stores, chat databases, home directories, or unrelated project history unless the user explicitly names them.
Workflow
- Define the work period, audience, and sources. State any important missing evidence.
- Gather goal statements, plans, tracker state, changed artifacts, validation output, corrections, decisions, failed attempts, and unfinished work.
- Build a factual timeline before interpreting success or friction.
- Analyze with [
references/analysis-rubric.md](references/analysis-rubric.md). Separate outcome quality from process quality. - Draft with [
references/retro-template.md](references/retro-template.md). Omit inapplicable sections instead of writing filler. - Tie each lesson to evidence and a repeatable action. Keep proposed skills or safeguards specific enough to implement.
- Present the retrospective in the requested location. Do not create a permanent retro file unless the user asked for one.
Rules
- Distinguish original goals from later pivots.
- Credit smooth work and successful corrections alongside failures.
- Describe mistakes and communication friction neutrally, with the information available at the time.
- Do not invent message counts, timing, files changed, or causal explanations.
- Quote only short excerpts that materially establish a lesson.
- Exclude credentials, tokens, cookies, private keys, and unrelated personal data.
- Prefer two or three high-value improvements over a long generic suggestion list.
Output
Produce a self-contained retrospective with sources, confidence limits, concrete evidence, and prioritized follow-up actions.
Use [agents/analyst.md](agents/analyst.md) for an independent retrospective pass.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/skill-tap
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.