Vp Retro

Reflect on a recent agent session to find evidence-backed improvements to collaboration, instructions, skills, or workflow. Boundary: not a code or PR review.

VdustR 30509e6 4 files · 2.5 KB Updated

File contents

Session Retrospective

Start from observed friction, corrections, repeated work, uncertainty, and successful shortcuts. Distinguish a one-off event from a reusable pattern.

Use interactive questions to test why an event happened and where the smallest durable fix belongs: current prompt, personal instructions, repository guidance, skill, automation, tool, or no persistent change.

Recommend changes only when the expected benefit exceeds the added context and maintenance cost. Prefer deleting or narrowing guidance over adding another duplicate rule. Do not update instructions, skills, or memory without explicit authorization.

Read references/dimensions.md for analysis lenses and references/subagent-guide.md only when delegated evidence gathering is useful and permitted.

Related skills

  • vp-session-wrapup when the session needs operational closeout in addition to reflection.

VdustR/skills/tree/main/skills/vp-retro commit 30509e6107

Frequently asked questions

npx skillmds@latest add vdustr/vp-retro