backlog

Organize project backlog items as discrete Markdown files with YAML frontmatter to enable precise state tracking, sorting, and cross-reference for agile project-management workflows. This enforces a consistent schema for readability and tooling compatibility.

Track agile backlog lifecycles by managing standalone Markdown files through ready, add, list, pick, and archive commands. This enforces a consistent frontmatter schema for lifecycle-aware governance and item-tracking across per-epic planning.

Add and archive backlog items by creating a self-contained Markdown file and running the archive command. This lifecycle-aware workflow enforces a YAML frontmatter schema to maintain consistent state management across item-tracking operations.

This backlog approach works for lightweight agile task capture by turning scattered ideas into structured standalone Markdown files. It provides lifecycle-aware commands to manage items within Cortex's workflow orchestration for per-epic planning.

Use YAML frontmatter for backlog item state management because it enforces a consistent schema across files, enabling precise state tracking, sorting, and cross-reference. This makes backlog items easy to review, update, and reference.

You should not use standalone Markdown files for project backlog tracking if your workflow requires a centralized database rather than file-based state management, as this approach relies on discrete files and a strict YAML frontmatter schema for lifecycle orchestration.