Garrytan Gstack Retro

---
name: retro
description: 'Weekly engineering retrospective. Analyzes commit history, work patterns,

  and code quality metrics with persistent history and trend tracking.

  Team-aware: breaks down per-person contributions with praise and growth areas.

  Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".

  Proactively suggest at the end of a work week or sprint. (gstack)'
---

# retro

Resolve `scripts/entry.py` relative to this SKILL.md, then invoke it by absolute path:

Set `SKILL_DIR` to the absolute directory containing this file, as supplied by skill discovery.

```sh
python3 "$SKILL_DIR/scripts/entry.py" instructions --host cursor --skill retro
```

Use `claude-code`, `cursor`, `codex`, `openclaw`, or `hermes` for the current platform.
Follow the returned runtime contract and read the complete referenced workflow before acting.
Repeat the returned environment prefix on each shell call; variables do not persist between tool calls.
If setup is missing, explain the exact preparation command and obtain consent before downloads or builds.
Never silently use another gstack installation. Preserve the source workflow's questions and permission boundaries.