npx claudepluginhub tslateman/claude-plugins --plugin duetThis skill uses the workspace's default tool permissions.
Reflect on the work just completed in this conversation. Extract insights, not summaries.
Guides strict Test-Driven Development (TDD): write failing tests first for features, bugfixes, refactors before any production code. Enforces red-green-refactor cycle.
Guides systematic root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Guides A/B test setup with mandatory gates for hypothesis validation, metrics definition, sample size calculation, and execution readiness checks.
Reflect on the work just completed in this conversation. Extract insights, not summaries.
Identify 2-4 concrete technical insights from this session:
Focus on insights, not a summary of actions taken.
Surface 2-4 open threads worth considering:
Be specific—name files, functions, or concepts rather than speaking abstractly.
Before asking about persistence, check the current project's MEMORY.md:
If issues are found, include them in the question to the user -- e.g., "MEMORY.md has 3 stale items. Want to prune them while persisting new insights?"
After generating the retro, ask the user if any insights are worth persisting to auto memory. Use AskUserQuestion with options like "Yes, update MEMORY.md", "Yes, and prune stale items", and "No, just this session".
If yes, read the current MEMORY.md from the project's auto memory directory and intelligently merge the new insights—don't duplicate existing points, add new ones under the appropriate sections.