stale-proposals

# Stale Proposals An open proposal is a claim that something still needs doing. That claim decays two ways: the work quietly shipped under a different name and nobody flipped the status, or the idea simply stopped mattering. Both leave the queue lying, and the lie is expensive here — the heartbeat re-fires every open proposal on each wake, so a stale entry costs tokens forever and trains the operator to ignore the whole list. This skill reconciles the queue against what actually shipped. It is deliberately asymmetric about trust: **shipping evidence can close a proposal automatically, age cannot.** Evidence is checkable and a wrong flip is recoverable by reading the changelog; "this feels inert" is a judgement about the operator's intentions, and getting it wrong silently buries live work. ## Usage `/stale-proposals [--no-apply] [--from PROP-NNN] [--status proposed,deferred]` - **No arg** — full audit; auto-resolves unambiguous matches, asks about everything else. - **`--no-apply`** — report only, write nothing. Use when you want to see the verdicts before trusting them. - **`--from PROP-NNN`** — only proposals numbered NNN and up. Operator phrasings like "just PROP-100+" or "the newer ones" mean this flag. - **`--status <list>`** — only the listed open statuses. "Only the proposed ones" means `--status proposed`. Scope flags go to the collector in Step 1, so the bundle itself is narrowed and the evidence floor moves with it. Never scope by prose in the subagent contrac...