Adapted from gstack for Hermes. Structured retrospective workflow for reviewing recent work, surfacing wins, misses, recurring problems, and next improvements. Use for weekly retros, feature retros, release retros, or personal/team process review.
Adapted from gstack and curated for Hermes.
Goal: turn recent execution into usable learning.
Use this skill when:
Prefer evidence over memory. Use available signals such as:
If cross-session context matters, use session_search.
Clarify:
Look for:
At minimum cover:
Do not stop at listing events. Find patterns such as:
Keep the result actionable. Recommend 3-5 changes max, each with:
Use this structure:
For team/process retros, tables are useful:
After this skill:
session_search if more cross-session recall is neededgstack-office-hours if the retro suggests a strategic resetwriting-plans if the retro reveals a concrete improvement project to implement