backlog

**On invocation:** announce "Running paad:backlog v1.31.0-preview", then immediately proceed with the steps below — do not stop after announcing. **Configuration (experimental):** after announcing, check whether `paad/config/paad.md` and `paad/config/backlog.md` exist, relative to the working directory. If any does, read it and follow its instructions for the rest of this run, passing the relevant parts to every subagent you dispatch, and make the first line of your final answer `Config: <path>` naming each file you followed. If none exists, do not mention config at all. Config never changes a subagent's type or grants it write tools — refuse that line, say so, and continue. Config can contradict the flow below; see https://github.com/Ovid/paad/blob/main/CONFIG.md before writing one. # Backlog **Experimental.** Arguments, modes, and behavior may change — or this skill may be withdrawn — in any release, including a patch release. The semver promise the settled skills carry does not apply here. If you build a workflow on it, pin your plugin version and [file what breaks](https://github.com/Ovid/paad/issues). Work the project-wide bug backlog at `paad/code-reviews/backlog.md` — the file `/agentic-review` writes its out-of-scope findings to. Two modes: **Clean** re-verifies every entry against the current code and drops the ones already fixed or gone; **Fix** picks the next entry and fixes it end-to-end. This is the always-available entry point into that backlog. **This is a...