ccc-tasks

$ccc-tasks — Markdown task tracking

CC Commander · $ccc-tasks · one file, markdown checkboxes, a git-visible audit trail

When to use / when not to

• Use for personal projects that do not need a tracker, side-session tracking while a larger ticket is in flight, brainstorm capture before picking one or two to execute, and a reviewable audit trail in git.
• Team coordination with two or more people: use $ccc-linear.
• Long-term milestones: use a tracker project.
• Sub-tasks of a complex feature: use the feature's spec doc and the session's task tool.
• In Codex, ask each picker below as a plain-text question with the same options.

File format

tasks/todo.md in the project root:

# Todo

## Active

- [~] P0 · Ship the release candidate
  - note: smoke test passes locally, CI pending
- [ ] P1 · Add retry to the webhook handler
- [x] P0 · Fix silent MCP startup failure ✅ 2026-04-23

## Blocked

- [!] P1 · Launch post — waiting on the demo recording

## Someday

- [ ] Editor companion extension

Priorities: P0 this week · P1 this month · P2 this quarter · P3 someday.

Status: [ ] todo · [~] in progress · [x] done (with date) · [!] blocked (with a blocker note).

What happens

1. Read the file

test -f tasks/todo.md && cat tasks/todo.md || echo "no tasks/todo.md"

Missing: ask with AskUserQuestion "🟢 Create tasks/todo.md with the empty sections" or "Cancel". Create it with Write only on yes. This is the only time the skill writes the whole file.

2. Route by argument

$ARGUMENTS	Step
empty, list	Show Active and Blocked, then step 3
pick	Step 3
add	Step 4
done	Step 5
prune	Step 6

3. Pick one to work on

Ask with AskUserQuestion: up to 4 open items, P0 first, the recommended one first and marked 🟢, each description naming its priority and section. On pick, move it under Active if it is not there, mark it [~], and state the scope in one sentence.