task-management

Markdown task tracking uses a four-state lifecycle (TODO, IN_PROGRESS, DONE, STALE) to manage files. Each task transitions through these states, requiring YAML frontmatter with status and timestamps to ensure complete traceability and auditability.

Automating task tracking with individual Markdown files eliminates scattered information by storing each task independently. A centralized INDEX.md provides an overview, while deterministic IDs (TASK-YYYY-MMDD-NNN) ensure easy tracing and ordering across workflows.

To create a new task, generate a daily deterministic ID (TASK-YYYY-MMDD-NNN) and write it as a TODO Markdown file under the tasks directory. You then update the central INDEX.md to register the new task and maintain an accurate overview.

Yes, file-based task management supports both personal and team productivity workflows. By utilizing per-task Markdown files with a transition log and a central archive for completed or stale tasks, it ensures auditability and clear traceability for any collaborative scale.

Markdown tasks enter the STALE state due to inactivity during lifecycle tracking. This optional state sits alongside the standard TODO, IN_PROGRESS, and DONE states, ensuring inactive tasks are archived rather than cluttering the active workflow overview.

Task management files require YAML frontmatter and a transition log to guarantee auditability. The frontmatter records status and timestamps, while the transition log documents every state change, ensuring complete traceability and deterministic tracking for each task.