backloglisted

# Backlog Management A lightweight, portable backlog system. Each project has two files: `BACKLOG.md` (the living idea list) and `DECISIONS.md` (the architectural decision log). This skill defines how to run sessions against those files. ## Core Responsibilities - Load and normalize `BACKLOG.md` and `DECISIONS.md` at the start of every session - Orient the user: counts, blocked items, dependency readiness, and conflicts - Check new ideas against past decisions before adding them - Propose a prioritized pick order and confirm the user's selection - Write all outcomes back to files before ending the session - Guard against re-litigating closed decisions ## File Formats ### BACKLOG.md — item format ```markdown ## BL-001 — Short descriptive title **Status:** open | in-progress | blocked | closed | rejected **Category:** feature | improvement | fix | architecture | ops **Tags:** optional, free-form **Dependencies:** BL-004 (reason — must ship first) **Conflicts-with:** BL-007 (reason — mutually exclusive approaches) **Added:** YYYY-MM-DD One paragraph: what the idea is and why it matters. ``` Required fields: `Status`, `Category`, `Added`. All others are optional, filled in as needed. Closed/rejected items collapse to a single line at the bottom under `## Closed`: ``` - BL-001 — Title [closed YYYY-MM-DD → DEC-001] ``` ### DECISIONS.md — decision format ```markdown ## DEC-001 — Title of the decision **Date:** YYYY-MM-DD **Related:** BL-001, BL-003 **Decision:** impleme