groom

Audits Sidequest boards for completed, superseded, duplicated, stale, or missing repository work tickets.

15|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill groom-eigenwise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: groom
Source: https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/groom
Command: npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill groom-eigenwise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you audit a Sidequest board for work that is already done, no longer relevant, duplicated, or safely reclaimable so the board stays accurate without deleting history or disturbing active work.

Core Features & Use Cases

  • Completed ticket cleanup: Closes tickets that are already shipped, with evidence-based comments.
  • Superseded and duplicate handling: Identifies tickets replaced by newer decisions or overlapping requests and closes the redundant ones safely.
  • Dead claim recovery: Releases reclaimable claims when an agent has stopped, gone idle, or abandoned the task.
  • Missing work discovery: Finds repo changes that were never ticketed and files them for tracking.
  • Interactive judgment calls: Escalates unclear cases to the user instead of guessing, then applies the chosen resolution.

Quick Start

Ask the assistant to run a grooming pass on a Sidequest board, identify done, duplicate, stale, and missing-ticket work, and safely close or file only the cases backed by evidence.

Frequently Asked Questions about groom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up a Sidequest board with stale or completed tickets?

You can clean up a Sidequest board by running an evidence-based grooming pass that audits for completed, superseded, duplicate, or stale tickets, then safely closes them while preserving project history and active work.

What is evidence-based repository grooming for project boards?

Evidence-based repository grooming is an auditing process that identifies done, duplicate, stale, or missing tickets on a project board, requiring strict proof before closing or filing items instead of blindly deleting them.

How do I release dead claims from abandoned agent tasks in a repository?

To release dead claims, audit the Sidequest board for reclaimable claims where an agent has stopped, gone idle, or abandoned a task, safely recovering them without disturbing active work.

Can I find and file missing repository changes that were never ticketed?

Yes, during a board grooming session, the audit can discover repository changes that were never ticketed and file them for tracking, ensuring complete gap filing across the project board.

How does the board cleanup tool handle unclear or duplicate tickets?

For unclear or duplicate tickets, the tool escalates judgment calls interactively to the user instead of guessing, then applies the chosen resolution to safely close redundant or superseded items.

Does the ticket audit permanently delete closed or superseded work?

No, the ticket audit applies strict non-deletion handling, meaning completed, superseded, and duplicate tickets are closed with evidence-based comments rather than being permanently removed from the board.