retrospective
Retrospective
Reflect on what happened. Identify what blocked agent autonomy. Produce concrete improvements so the system gets better.
Not tied to sprints or calendars. Run a retro when there's something worth learning from: a feature shipped, an incident resolved, a pattern of failures, a project wrapped.
Core Question
What happened that an agent couldn't handle autonomously, and what's the cheapest fix so it can next time?
Process
- Identify the trigger
- Gather evidence
- Analyze through the autonomy lens
- Capture learnings
- Create improvement tickets
- Append to .tap/learnings.md
More from teambrilliant/tap-skills
systems-health
Measure the health of a software development system using stocks, flows, and feedback loops. Use when someone says "systems health", "how's the project going", "health check", "measure our process", "are we shipping fast enough", "what's slowing us down", or for periodic check-ins on development velocity and quality. Pulls data from git, GitHub, and CI to diagnose what's working and what's broken. Outputs to .tap/system-health.md.
2blast-radius
Analyze the impact surface of a PR or set of changes before merging. Use when someone says "blast radius", "review this PR", "what does this change affect", "is this safe to merge", "impact analysis", or after an agent opens a PR that needs human verification. Maps what changed, what else is affected, what could break, assigns risk level, and generates a manual verification checklist. The human gate for mixed human-agent teams.
2tap-audit
Assess how ready a repository is for autonomous agent work. Use when someone says "audit this repo", "tap audit", "how ready is this codebase", "assess this project", or when an agent enters an unfamiliar codebase and needs to understand it before working. Scans documentation, MCP servers, CLI tools, permissions, test infrastructure, environments, and process to produce a readiness assessment with actionable leverage points. Outputs to .tap/tap-audit.md.
2