| name | backlog_manager |
| description | Interactive Improvement Backlog widget with kanban status management, filtering data, notes, and local item creation without mutating Ouroboros core memory directly. |
| version | 0.1.0 |
| type | extension |
| runtime | python3 |
| entry | plugin.py |
| permissions | ["route","widget","tool"] |
| env_from_settings | [] |
| when_to_use | User wants to inspect, triage, add, annotate, or manage Ouroboros improvement backlog items from a reviewed widget. |
| timeout_sec | 60 |
| ui_tab | {"tab_id":"backlog","title":"Backlog Manager","icon":"list-checks","span":2,"render":{"kind":"declarative","schema_version":1,"components":["[Truncated]","[Truncated]","[Truncated]","[Truncated]","[Truncated]"]}} |
Backlog Manager
Backlog Manager is a reviewed extension widget for triaging Ouroboros's Improvement Backlog.
It reads memory/knowledge/improvement-backlog.md as the source backlog and stores user-facing management state in this skill's own state directory (overlay.json). The overlay contains status overrides, notes, and locally-created items. This keeps the core backlog pipeline untouched: execution reflections can continue appending to the source file while the widget provides an interactive working view.
The UI is rendered as a host-owned kind: declarative widget (schema v1). Components are Kanban-first: a polling refresher seeds the backlog state, then a compact kanban board (Open / In progress / Deferred / Done / Wont fix) supports drag-and-drop between columns through /api/extensions/backlog_manager/move. Stats appear as a small key/value strip beneath the board, followed by short forms for adding items and updating status / appending notes. No arbitrary JavaScript is loaded.
Boundaries
- Does not mutate the self-modifying repo.
- Does not overwrite
memory/knowledge/improvement-backlog.md.
- Writes only to the skill state directory.
- New widget-created items live in the overlay until a future core backlog API exists.
- Non-trivial implementation work still requires
plan_task before code changes, as the backlog item itself may request.
