| name | cleanup-commissions |
| description | Review completed commission artifacts as a batch, extract loose threads into a retro, and delete the commission files. Use after a feature's implement-review-fix cycle completes, before creating a PR, or when .lore/work/commissions/ (or the flat-layout .lore/commissions/) has accumulated files that no longer represent active work. Triggers include "clean up commissions", "commission cleanup", "review commissions", "batch cleanup". |
Cleanup Commissions
Review completed commission artifacts as a batch, extract loose threads into a retro, and delete the commission files. Git history preserves the originals.
Core Principle
Commissions form work chains: issue, spec, plan, implement, review, fix. A finding in one commission is usually consumed by the next in the chain. Don't extract things that were already addressed. The only value worth preserving is:
- Loose threads - findings that fell off the chain (deferred and never picked up)
- Infrastructure patterns - systemic issues in the commission system itself
- Cross-cutting lessons - patterns visible only when reviewing the full batch
Process
1. Inventory
Scan all commission files. New commissions live in .lore/work/commissions/; flat-layout commissions under .lore/commissions/ may also be present in projects that have not migrated. Treat both directories as one set. For each, capture:
- Worker name, date, title, status, type (from frontmatter)
- Whether it completed, failed, or was abandoned
Skip artifacts with type: scheduled. Scheduled commission artifacts are recurring schedule definitions, not individual work units. Only type: one-shot (or no type field, which defaults to one-shot) artifacts are eligible for cleanup.
Spawned commissions (one-shot artifacts with a field) are eligible for cleanup. The field provides provenance context, which is useful for grouping spawned commissions by their parent schedule when reviewing the batch.
