todo-create

File-based todo tracking centralizes technical debt and code review feedback into markdown files with YAML frontmatter, preventing context loss and ensuring traceability across multiple sessions.

Creating a durable todo item involves writing a markdown file to the canonical .context/compound-engineering/todos/ directory, populated with YAML frontmatter containing status, priority, issue_id, dependencies, and tags to structure the work item.

Triage feature requests and technical debt by leveraging a YAML frontmatter schema with status, priority, and dependencies fields, allowing structured sorting and cross-session tracking within a canonical directory.

Yes, the system reads from the legacy todos/ directory while enforcing all new writes to the canonical .context/compound-engineering/todos/ directory to maintain a consistent and auditable history.

Documenting a proposed solution requires structured markdown sections for Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, and Work Log to ensure comprehensive and auditable technical documentation.

Cross-session todo tracking loses context without a standardized file structure because missing YAML frontmatter and a canonical directory prevents consistent triage, dependency tracking, and auditable history across sessions.