backlog-quick-reference

Use the Backlog.md CLI to create tasks with the command structure: specify task title, description, and acceptance criteria as flags or arguments. The CLI generates files following the `task-{id} - {title}.md` naming pattern and stores criteria in standardized metadata, ensuring proper synchronization and workflow enforcement.

Task files must follow the `task-{id} - {title}.md` pattern strictly. This naming convention is critical for CLI functionality and metadata synchronization. Manual edits to filenames disrupt workflow; all task operations must use CLI commands to maintain this pattern.

All task operations—creation, editing, status updates, and metadata changes—must go through CLI commands. Manual file edits are prohibited because they break metadata synchronization and violate the enforced workflow rules that keep your backlog consistent and queryable.

Use CLI commands to add, check, uncheck, or remove acceptance criteria. Implementation plans and notes are stored as standardized metadata within task files. The CLI enforces correct formatting and prevents corruption from direct editing.

Backlog.md enforces CLI-based workflows with strict file naming, mandatory metadata conventions, and standardized task operations. These rules prevent accidental data loss, ensure consistent task state, and enable reliable synchronization across your project management processes.

The Backlog.md CLI provides dedicated commands to modify task properties like status, assignees, and labels. Each operation updates task metadata consistently within the `task-{id} - {title}.md` file structure, maintaining workflow integrity without manual file edits.