mark-deferredlisted

Mark all pending discovered-scope findings as deferred with a one-line reason that names a concrete WHY. Use when the discovered-scope gate flags advisory-specialist findings you have consciously decided cannot ship in this session — typically because they require a separate specialist, a database migration, a stakeholder decision, or context not yet loaded. Each deferred row is timestamped and the reason is recorded so the gate stops blocking and `/ulw-report` can audit deferral patterns later. **Prefer wave-append over deferral when the finding is same-surface to your active work** — see *When NOT to use* below.
X0x888/oh-my-claude · ★ 3 · Code & Development · score 79

Install: claude install-skill X0x888/oh-my-claude

# Mark Pending Findings Deferred > **v1.40.0: refused under ULW execution intent by default (`no_defer_mode=on`).** When ULW is active AND `task_intent=execution`, this skill exits with a 2 and a recovery message. The validator-WHY loophole that let "blocked by Waves 4-12 wave-plan rollout" pass as a legitimate reason is closed at the source — the answer to "should the model defer under /ulw?" is no. Under ULW, address each finding inline, wave-append it to the active plan, or — for genuine not-a-defect cases only — flip its status to `rejected` with a concrete WHY via `record-finding-list.sh status`. The skill remains usable in advisory/continuation intents, in non-ULW sessions, and under the user-opt-out `no_defer_mode=off`. The rest of this document describes the legacy soft-validator behavior; it applies when `no_defer_mode` is off or the intent isn't execution. Bulk-update every `pending` finding in the current session's `discovered_scope.jsonl` to `deferred` with a one-line reason. The discovered-scope gate counts only `pending` rows, so once you defer the rest, your next stop attempt passes through. The deferred rows are kept (not deleted) so you and `/ulw-report` can see what was triaged versus what was shipped. **Important — `/mark-deferred` is the LAST resort, not the first.** The discovered-scope gate offers four ways to address a finding (under non-ULW conditions where this skill is still callable): 1. **Ship it** — fix the finding in this session and referenc