retro
Run a retrospective that produces action items, not just observations. A retro without specific next steps is a venting session.
Principles — hold these throughout:
- Blame-free. Focus on systems, processes, and circumstances — not people. "The deploy process let a bug through" not "Bob broke prod."
- Actions over observations. Every theme must produce a concrete change. If it doesn't lead to action, note it and move on.
- Max 3 action items. More than three won't get done. Prioritize ruthlessly.
Step 1: Set Context
Establish the boundaries before gathering input:
| Question | Answer |
|---|---|
| What period/project? | Name it specifically — "Sprint 14" or "Billing v2 launch" |
| What was the goal? | What were we trying to accomplish? |
| What actually happened? | State the outcome factually — shipped on time, missed by 2 weeks, hit metrics, didn't |
| Who was involved? | List the team so contributions are visible |
| Timeline | Start date, end date, key milestones |
More from kazdenc/builder-skills
design-brief
One-time setup that gathers design context for your project and saves it to your config file. Run once to establish persistent design guidelines.
31prd
Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and edge cases. Use when user says "write a PRD", "product requirements", "requirements doc", "spec this feature", "document requirements", or needs to define what to build and why.
17critique
Evaluate design effectiveness from a UX perspective. Use when user says "critique this design", "review the UX", "give design feedback", "is this good design", "design review", "evaluate this layout", or wants expert evaluative feedback on visual hierarchy, information architecture, and emotional resonance.
14security-scan
Check code for OWASP top 10 vulnerabilities including injection, XSS, auth issues, and secrets exposure. Use when user says "security audit", "check for vulnerabilities", "security scan", "is this secure", "OWASP check", "find security issues", or needs to verify code security before shipping.
13polish
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues. Use when user says "polish this", "final pass", "ready to ship", "fix the details", "pixel-perfect", "almost done", or when a feature is functionally complete but needs refinement.
13env-config
Set up environment variables across local, staging, and production with validation and documentation. Use when user says "set up env vars", "environment variables", "configure secrets", ".env setup", "env validation", or needs to manage configuration across environments.
12