todo-create

Manage durable cross-session todos stored as markdown files.

Updated Mar 26, 2026

Search Tags:#workflow #documentation #todo #triage #code-review #file-based #cross-session

Ready to run

npx skills add https://github.com/jaydubya818/New_baseline --skill todo-create-jaydubya818

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo-create
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/plugins/compound-engineering/skills/todo-create
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill todo-create-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

File-based todo tracking enables durable, cross-session work items to persist across sessions, allowing teams to manage findings, debt, and feature work without losing context.

Core Features & Use Cases

Canonical storage for todos under .context/compound-engineering/todos/ with a legacy read-only path at todos/
Todo templating and multi-session lifecycle, including triage, readiness, and completion
Integration with the Compound Engineering workflow to capture findings and action items across sessions

Quick Start

Create a new todo by following the canonical workflow in .context/compound-engineering/todos/ and filling the required sections.

Frequently Asked Questions about todo-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track cross-session todos so code review findings and technical debt don't get lost?▼

Cross-session todo tracking persists work items as markdown files under a canonical directory, ensuring triage findings, debt items, and feature tasks survive across sessions. Templates enforce consistent lifecycle stages from creation through completion.

What is file-based todo management and when do I need it for engineering workflows?▼

File-based todo management stores durable work items directly in your repository rather than volatile memory. It is needed when managing multi-session planning, triage, and code-review findings that require persistent context across team interactions.

How do I create a new todo item using the canonical file structure?▼

Create a new todo by following the canonical workflow in the designated todos directory and filling the required sections of the todo template. This establishes the item with a structured lifecycle for triage, readiness, and completion tracking.

Does todo-create work with existing todos in a legacy directory path?▼

The workflow supports a legacy read-only path for existing todos, allowing read access to prior items. New items must be created in the canonical directory structure to enable full multi-session lifecycle management and triage.

What is the best way to triage code review findings across multiple sessions?▼

The best way is storing findings as durable markdown files with templated lifecycle stages, enabling systematic triage and readiness tracking. This integrates with the engineering workflow to capture action items without losing context.

Are there limitations to using file-based todo tracking for large-scale project management?▼

File-based todo tracking is optimized for engineering workflows like code review and debt triage rather than broad project management. It lacks built-in notification or visualization features, relying entirely on markdown file structure for context persistence.