ceos-todos

ceos-todos

Track To-Dos — the concrete actions that bridge meetings and execution. Every To-Do has one owner, a due date, and a source. EOS teams target 90%+ weekly completion rate.

When to Use

• "Show my to-dos" or "what's on my list?"
• "Create a to-do" or "add a to-do for [person]"
• "Mark to-do done" or "complete [to-do]"
• "To-do review" or "how's our completion rate?"
• "What to-dos are overdue?"
• "Open to-dos" or "what needs to get done this week?"
• "To-do list" or "show all to-dos"
• "Weekly to-do report" or "to-do scorecard"
• "New to-do from L10" or "IDS to-do"
• Any time someone commits to a concrete action with a deadline

Context

Finding the CEOS Repository

Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.

If .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."

Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.

Key Files

File	Purpose
data/todos/	To-Do files (one file per To-Do)
templates/todo.md	Template for new To-Do files

To-Do File Format

Each To-Do is a markdown file with YAML frontmatter:

id: todo-001
title: "Send revised proposal to Acme"
owner: "brad"
due: "2026-02-20"
status: open           # open | complete
source: l10            # l10 | ids | quarterly | adhoc
created: "2026-02-13"
completed_on: ""       # filled when status → complete

Status values:

• open — not yet done
• complete — done (binary — no partial credit in EOS)

Source values:

• l10 — created during an L10 meeting
• ids — created during IDS issue resolution
• quarterly — created during a Quarterly Conversation
• adhoc — created outside of a meeting context

Overdue: A To-Do is overdue if status: open and due is before today's date. This is computed when displaying — not stored as a status.