Analyzes a work session to extract retention insights and durable learnings.
npx skills add https://github.com/supertyrelle/pelley --skill retro-supertyrelle
Please help me install this Agent Skill. Skill: retro Source: https://github.com/supertyrelle/pelley/tree/main/skills/retro Command: npx skills add https://github.com/supertyrelle/pelley --skill retro-supertyrelle
This Skill turns the end of a work session into a structured retrospective, helping you understand what went well, what slowed progress, and what should change next time. It also persists durable learnings so future sessions benefit from accumulated experience instead of repeating the same mistakes.
Ask the retro skill to review this session and update project memory with the most important durable learnings.
High-intent search queries and answers about installing and using this skill.
Run a session retrospective by analyzing recent git activity, backlog status, and conversation context to extract actionable keep, stop, and try-next-time learnings. This reconstructs the session to identify what slowed progress and what went well.
Capturing durable engineering learnings after a milestone requires structured reflection on session velocity, quality, and blockers. Update project memory files to persist these insights so future sessions benefit from accumulated experience instead of repeating mistakes.
Yes, you can analyze git activity and conversation context together for session review. Reviewing both data sources alongside backlog status reconstructs what happened during the session, enabling actionable reflection on process blockers and discoveries.
You need a memory file to persist durable insights extracted from an engineering session. Updating memory with keep, stop, and try-next-time learnings captures concrete follow-up actions and ensures future work benefits from accumulated experience.
Automated engineering session analysis relies on inspecting git activity, backlog status, and conversation context. Limitations include dependency on the accuracy of these inputs and the requirement for manual learning lifecycle checks for optional follow-up actions.
goffityAnalyze git changes to generate retrospective drafts with Before/After context.
lithiumtoastGuide Agile retrospectives through Derby–Larsen's five stages and save actions to Markdown.
opensquillaManage durable recall and updates of OpenSquilla memory via USER.md and MEMORY.md files.
mkalhitti-cloudEnforce mandatory lessons-learned reviews before NinjaTrader code changes.
