projectbacklog

name	ProjectBacklog
version	0.1.0
description	Capture, list, update, and close repo-local backlog items as Obsidian Tasks lines in dated daily files under docs/todos/. USE WHEN capture todo, project todo, project backlog, repo backlog, backlog item, list todos, todo capture, new todo, close todo, or local issue tracking without GitHub.

ProjectBacklog

Repo-local backlog inspired by todo.txt, stored as Obsidian Tasks checkbox lines with Dataview inline fields. One markdown file per capture day, multiple todos per file. Queryable from Obsidian (Tasks plugin and Dataview), grep-able from the shell. Use this when an idea, defect, or follow-up should outlive the conversation but is too small for an ADR and too project-specific for the personal vault backlog.

Conventions

Location

docs/todos/YYYY-MM-DD.md — one file per capture day. Daily files are append-only logs. The date in the filename IS the created date for every item in the file.

Item format

Each todo is one Obsidian Tasks checkbox line followed by optional indented sub-bullets for context, acceptance criteria, and links.

- [ ] Short imperative description [priority:: high] [id:: 0001] #tag1 #tag2
    - Why this matters in one sentence.
    - Acceptance: bullet list of conditions for closing.
    - Related: [[0004 Some ADR]], #123, links to other todos.

Status markers

Marker	Meaning
- [ ]	open
- [/]	in progress
- [x]	done
- [-]	won't do / cancelled

Inline fields

Dataview [key:: value] syntax. Place after the description, before tags.

Field	Values
[priority:: ...]	highest, high, medium, low, lowest (default: medium)
[id:: NNNN]	required — 4-digit zero-padded stable id, unique across the project
[due:: YYYY-MM-DD]	optional deadline
[start:: YYYY-MM-DD]	optional earliest start date
[scheduled:: YYYY-MM-DD]	optional scheduled date
[completion:: YYYY-MM-DD]	set when status flips to [x]

The created date is implicit in the filename — never restate it as an inline field.

File layout

# Todos — 2026-04-27

- [ ] First todo of the day [priority:: high] [id:: 0002] #app
    - Acceptance bullets.

- [ ] Second todo of the day [priority:: medium] [id:: 0001] #docs
    - ...

Newest item at the top of the file. Items captured on later days go in their own dated files. Closed items stay in their original file with - [x] and [completion:: YYYY-MM-DD] — never deleted, never moved.

Capture Workflow

1. Resolve today's date and target file docs/todos/YYYY-MM-DD.md, creating the directory and file as needed. New files start with a # Todos — YYYY-MM-DD heading.

2. Scan all existing daily files for description overlap. If a related open item exists, propose updating it instead of duplicating.

3. Assign the next 4-digit id (max existing [id:: NNNN] across all daily files + 1, starting at 0001).

4. Insert the new item at the top of today's file with - [ ] status, the assigned id, and tags. Add indented sub-bullets only if acceptance criteria or context are non-trivial.

5. Report the id, file path, and line written.

List Workflow

Default view: open + in-progress, grouped by priority. Show id, description, age (days since created, derived from filename).

Update Workflow

1. Status transitions: [ ] → [/] → [x]. [-] is terminal. Reopening requires [x] → [ ] with a sub-bullet explaining why.

2. Never edit the [id:: NNNN] once assigned. Never move the item to a different daily file.

Close Workflow

1. Set the checkbox to [x] (done) or [-] (won't do).

2. Append [completion:: YYYY-MM-DD] for completed items.

3. Add a sub-bullet noting the closing commit, PR, or rationale.

4. Leave the item in its original daily file — the file represents the day the work was captured, not the day it closed.

Constraints

• Every item carries a stable [id:: NNNN] so external references (commits, ADRs, other todos) survive description edits.
• Sub-bullets are optional but encouraged when acceptance criteria are non-trivial. Trivial todos can be a single line.
• Use Dataview inline-field syntax ([key:: value]) for metadata, not emojis. The plain-text form is git-diff-friendly and survives non-Obsidian tooling.
• Don't introduce non-standard inline fields. Stick to Obsidian Tasks-recognised keys so third-party queries keep working.

@Example.md