retro
Engineering manager that runs a retrospective. Analyzes what shipped, what broke, what to improve. Tracks patterns across sprints. Use when: "retro", "retrospective", "what did we ship", "what went wrong", or at the end of a sprint/week.
- License 许可
- MIT
- 所属仓库
- kalash33/kstack
- 最近更新
- 2026-05-20
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- retro
- description
- Engineering manager that runs a retrospective. Analyzes what shipped, what broke, what to improve. Tracks patterns across sprints. Use when: "retro", "retrospective", "what did we ship", "what went wrong", or at the end of a sprint/week.
03 SKILL.md 正文
/retro — Eng Manager
What shipped. What broke. What to improve.
When to Use
- End of sprint or week
- After a major ship
- After an incident
- When you feel stuck
Process
Step 1: Gather Data
# What shipped this week/sprint
git log --oneline --since="1 week ago" --no-merges
# PRs merged
gh pr list --state merged --search "merged:>=$(date -v-7d +%Y-%m-%d)"
# Test health
{test_command} 2>&1 | tail -5
Step 2: Analyze
What went well?
- Features shipped on time
- Bugs caught before production
- Clean PRs (few review rounds)
What went wrong?
- Bugs that escaped to production
- Scope creep
- Blocked work
- Flaky tests
What to improve?
- Patterns that keep recurring
- Missing automation
- Knowledge gaps
Step 3: Report
## Retro: Week of {date}
### Shipped
- feat: notification triage (PR #42)
- fix: duplicate delivery bug (PR #43)
- docs: API reference update (PR #44)
### Metrics
- PRs merged: 3
- Tests added: 9
- Coverage: 83% → 87%
- Bugs escaped to prod: 0
### What went well
- /qa caught the duplicate delivery bug before ship
- Plan doc kept scope tight
### What to improve
- Queue worker has no monitoring — add /perf next sprint
- Test coverage on src/queue.ts still below target
### Action Items
- [ ] Add monitoring to queue worker
- [ ] Write integration tests for queue
Chaining
- Before:
/ship(retro after shipping) - After:
/plan(retro findings inform next sprint)
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.