backlog-manager

name	backlog-manager
version	1.0
description	Manages an outcome-focused backlog stored in /work/backlog.md. Handles command-driven operations to add, refine, list, start, complete, and archive work items. Each item is tracked with a status, creation date, and a clear observable outcome statement. Use when asked to manage a backlog, add work items, or check what to work on next.

Backlog Manager

When Not to Use

• When the task is to execute ready items and perform the actual work they describe — use backlog-worker instead
• When the project requires complex dependency tracking between items
• When multiple people need concurrent write access (this is a single-file, single-user system)
• When risk tracking, resource allocation, or sprint planning are required
• When the work is exploratory and outcomes cannot yet be stated (use a notes file instead until outcomes can be defined)

---

Interaction Protocol

On ambiguous commands, ask before acting:

• If Add input lacks a clear outcome, ask: "What does success look like for this item?"
• If Refine input is unclear, ask which specific aspect to improve: Outcome, Context, or Notes

Output style:

• List and Next: plain text only, no commentary
• All other commands: confirm the action taken in one sentence, then show the updated item
• Do not volunteer prioritization opinions or suggest what to work on unless Next is called

---

Inputs and Outputs