declinedlisted

Look up the registry of declined and deferred decisions, so the same idea is never re-pitched: what was rejected, why, and under what condition to revisit. Read-only, and can also run the detector for new rejections in recent sessions. Triggers: "/declined", "did we reject this before".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

OBJECTIVE: Show the registry of declined/deferred decisions (what · why · revisit-if) BEFORE (re-)pitching an idea — the anti "step on the same rake twice" guard. READ-ONLY: it writes nothing into the registry (the nightly scan and the human do that). CONTEXT: - The canonical registry (this hub): `%USERPROFILE%\.claude\projects\<hub-project>\memory\declined-decisions.md` (a copy exists in the laptop project — always read the hub one). - The nightly detector: `$IMPORTS_ROOT/declined-scan/declined_scan.py` (scheduled task "Declined-Decisions Nightly Scan", ~03:45) — it catches new refusals from fresh sessions and parks them on the AUTO-CAPTURED shelf. - The rule (cross-actor): rejected or deferred a proposal → record it in the registry. The canon for human assistants lives in the Bible as the "record a rejected decision" rule. STEPS: 1. Read `declined-decisions.md` (the hub path above). 1b. **Dead-man check on the watchdog** (added 2026-07-04; catches the class "the task was silently disabled", as happened 06-22→06-27): read `$IMPORTS_ROOT/declined-scan/highwater.json` → if `updated` is older than 2 days the nightly watchdog is NOT running → check `(Get-ScheduledTask -TaskName 'Declined-Decisions Nightly Scan').State`, enable it (`Enable-ScheduledTask`), and report in one line. Fresh → move on silently. 2. If the operator asked about a SPECIFIC topic — grep the registry for it and show the matches (what was rejected · why · under what condition to revisit). 3. Otherwise — a s