Capture Learnings and Run Retrospectives

Captures what works and what doesn't so every session builds on the last. /retro runs a weekly engineering retrospective with shipping streaks, test health trends, and growth opportunities. /learn lets you manage what gstack learned (patterns, pitfalls, preferences) across sessions. Together they turn ad-hoc debugging into a knowledgebase that speeds up future work.

1. Run /retro weekly to see what your team shipped, test health trends, and growth signals. 2. During work, use /learn to review, search, or prune project-specific patterns that gstack discovered. 3. On bugs or design decisions, gstack auto-logs learnings (confidence 1-10) for future sessions. 4. Learnings compound: next time you hit a similar bug, gstack suggests the pattern from the knowledgebase. Output: a retrospective report and an ever-growing project knowledge base that makes future work faster.

Learnings persist in ~/.gstack/projects/{slug}/learnings.jsonl (JSONL format, one learning per line). Learning decay is time-based (updated on each query). Cross-project learnings require opt-in via gstack-config set cross_project_learnings true. Retro data comes from the project's git log, test output, and gstack timeline logs.