todo-create

To track durable todos across sessions, you use a file-based markdown system that persists work items beyond a single editing session. This approach saves items to a canonical directory, ensuring tasks and findings survive session restarts.

The best way to triage code review findings is using a structured markdown template with standard frontmatter. This template guides you through documenting the problem statement, findings, and action items to ensure consistent resolution tracking.

You create a cross-session todo by filling out a 3-part markdown template and saving it to the canonical path at .context/compound-engineering/todos/. This enforces a standard structure for problem statements and action items.

No, this markdown todo system requires no external dependencies. It relies entirely on a file-based structure with standard frontmatter and canonical paths to organize and persist work items natively.

A file-based todo system keeps durable work items directly within your engineering workspace. This enforces a canonical write path and standard frontmatter, ensuring triage and resolution context persists locally alongside your code.

You need a cross-session todo tracking system when code review findings and action items must persist beyond a single editing session. It prevents losing triage context by saving structured markdown files to a canonical directory.