Groove Work Compound

After you close a work session or finish a task, this captures what you learned and updates your project's rules, templates, and docs to reflect it. It scans the conversation for mistakes, workflow patterns, and deferred decisions, then produces a checklist of what got documented. If you hit the same snag twice, it wants to know why and bake the fix into your setup. The optional rating prompt at the end keeps a simple signal log of how well your process is working. It's maintenance hygiene for teams serious about compounding their lessons instead of relearning them.

skills.sh installs: 540
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-work-compound --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-work-compound

Scope

"This conversation" means the full chat thread (all messages in the same chat where the user invoked compound). Lessons and compound actions come from work done or decided anywhere in that thread.

In scope:

Work done earlier in the same chat: other skill runs (e.g. /ppp-weekly-report, /groove-work-plan), file or bean edits, decisions, review or planning discussion.
Any bean or work item the user or the thread refers to as part of the workflow (e.g. the epic or task this compound stage belongs to). Use those to ground lessons and actions.

Not in scope unless the user asks: Daily memory, weekly summaries, or other docs (e.g. "compound on the whole day").

If no other work is visible in the context when compound runs (e.g. the turn only shows the compound request): ask which session or work to compound on (e.g. "I only see the compound request. Which session should I compound on — e.g. the PPP run above, or something else?") instead of concluding "no work discussed."