backlog

backlog

The repo-local backlog is a single markdown file the user co-maintains with AI assistants. It is not a Jira/Linear/GitHub-issues replacement — it's a low-friction capture surface for solo or AI-assisted projects.

File location

Search in this order and use the first one found:

1. ./backlog.md
2. ./Project Management/backlog.md
3. ./docs/backlog.md
4. ./.claude/backlog.md

If none exist, ask the user where to put it (offer the first option as default), then create it from the template at ${CLAUDE_PLUGIN_ROOT}/../../templates/backlog.template.md (relative to this skill; resolve via the plugin's templates/backlog.template.md).

File format

# Backlog

Lightweight TODO file co-maintained with AI assistants.

## Statuses
- 🔴 Blocked
- 🟡 In Progress
- 🟢 Ready
- ⚪ Backlog
- ✅ Done (archive monthly)

---

## <status-emoji> <Title>
- **Priority**: High/Medium/Low
- **Area**: <subsystem or repo>
- **Description**: <what>
- **Context**: <why / background>
- **Acceptance Criteria**: <when is it done>

What to do

When asked to show the backlog

Read the file and list every non-✅ item with its status emoji, title, priority, area. Group by status, ordered: 🟡 → 🔴 → 🟢 → ⚪. Don't dump the full body of every item — give a one-line summary; quote the full body only if the user asks about a specific one.

When asked to add an item

Capture:

• title (required — short, imperative)
• status (default ⚪ Backlog unless user signals otherwise)
• priority (ask if not obvious from context)
• area (infer from the conversation; e.g. current repo/folder)
• description, context, acceptance criteria (draft from the conversation; show to the user before appending)

Append to the file under ## Current Active Items (creating the heading if missing). Use the Edit tool, not Write — preserve existing content.

When asked to update an item (status change, edit)

Locate by title (fuzzy ok). Confirm the match if there's ambiguity. Use Edit to change status emoji or fields in place. When marking ✅ Done, move it under a ## Done section near the bottom (create if missing).

When asked what's on the backlog without a verb

Default to "show". Lead with 🟡 In Progress items.

Don't

• Don't suggest filing backlog items as Jira/Linear tickets unless the user explicitly asks. This backlog is the destination, not a staging area.
• Don't reformat the whole file silently. Targeted edits only.
• Don't create the file without asking where the user wants it.