Backlog

Backlog — Task Files

A Task File Backlog System: every card is one Markdown file with frontmatter, living in this folder. It reuses the [[adr/README|ADR]] philosophy — frontmatter-as-metadata, Obsidian Bases/graph friendly, copy-a-template discipline — applied to lightweight, mutable work items instead of frozen decisions.

The system is always passive: it sits ready to capture work, questions, and ADR resolutions — including turning a poor, vague prompt into a well-formed card or a Draft ADR. It is operated by the cotton-coveris-backlog teammate (Opus·low) and fed by the cotton-coveris-live-docs sentinel (Haiku), which hands it drafts whenever it detects spec drift just before a commit.

Three kinds, one backlog

All cards are identical in shape — only the filename prefix and the matching kind field/tag change:

Kind	Filename	What it is
ISSUE	`ISSUE-YYMMDD-xx.md`	Something to fix — bug, defect, chore, debt.
FEATURE	`FEATURE-YYMMDD-xx.md`	New functionality to build.
IDEA	`IDEA-YYMMDD-xx.md`	A proposal / exploration / spike — not yet committed work.

Conventions

Filenames are coded, never descriptive: <KIND>-YYMMDD-xx.md — YYMMDD = date of created; xx = 2-digit counter per kind per day. No slugs, no “weird names”.
Semantics live in tags + links + title, not in the filename — tags for everything. Every card carries tags: [backlog, <kind>] plus any area/topic tags, and uses [[wikilinks]] for cross-references.
Frontmatter per [[backlogs/template|the task template]] — id, title, kind, status, priority, area, created/updated, related, paths, tags.
Track work by file: related wikilinks the vault notes a card implicates (ADRs/PRD/API); paths lists the repo files/globs it touches (code, outside the vault). The backlog board (backlog.base, embedded in the Index below) groups cards by status, area, kind, and by file — so you can see every open card on a given path.
Status lifecycle: backlog → todo → in-progress → done, with blocked as a side state.
Mutable, not immutable (unlike Accepted ADRs): a card evolves; done cards stay as history, never deleted.
This folder adds backlog (and the kind tags issue/feature/idea) to the vault’s tag color groups.

Backlog vs. ADR

A backlog card is a question or a unit of work; an ADR is a settled decision. When a card’s resolution turns out to be a real architectural decision, the backlog teammate drafts a new ADR from [[adr/template]] (status Draft) and links it — but an ADR is only Accepted with express user confirmation. The path is: poor prompt → card / Draft ADR → human confirms → Accepted.

Index

![[backlog.base]]

[!note] The live board above fills itself from card frontmatter; the table below is a static fallback.

Card	Title	Kind	Priority	Status	Area
[[ISSUE-260531-01]]	Banda violeta (PRESTACIÓN) y redefinición del azul vs ADR-001-c	issue	medium	backlog	design-system