Engineering Blueprint
Reflect & Learn
Weekly retros and cross-session memory
What problem does this solve?
Captures what shipped and patterns learned so every future session gets smarter. /retro analyzes commit history and writes a team-aware retrospective with per-person breakdowns, shipping streaks, test health metrics, and growth opportunities. /learn manages the learnings file: search for patterns, prune stale entries, export for team sharing. Learnings feed into other skills (they search before making recommendations and cite prior insights).
How does it work?
Run /retro at the end of each week. It analyzes commits, builds, shipping velocity, and test health, then writes a candid retrospective with specific praise, growth areas, and team metrics. Run /learn to browse what gstack has learned about your codebase: architectural patterns, pitfalls, decision history. Search for specific patterns or prune entries when referenced files no longer exist. Learnings are saved in the project's state directory and automatically promoted to the team if you export them.
Key Features
/retro
Per-person shipping breakdowns. Commits, LOC, test ratio, hotspot files, shipping streaks. Per-person growth opportunities.
/learn
Manage project learnings (patterns, pitfalls, preferences). Search, prune, export. Auto-cited by other skills before making recommendations.
About This Blueprint
- Industry
- Technology
More Blueprints to explore
ICP-Filtered Outreach Lists from G2 Buyer Intent
Stop wasting rep time on weak intent signals and mismatched accounts. The workflow ranks ICP-fit buyers by readiness, finds the right contact, and supplies tailored outreach angles for the strongest opportunities.
Ishani D.
Account Manager at G2