// Manage project task lists stored in to-do.json and to-do.schema.json, including bootstrapping a backlog, selecting the highest priority task with jq, and updating task statuses. Use when Codex needs to read or update a JSON task list.
Release preparation and publish workflow: run tests, bump version, tag, push, and create a GitHub release (and update Homebrew formula if present). Use when asked to cut a release, bump version, create tags, or publish a release.
Run a live Looper smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper behavior or demonstrating a live run.
Create clean git commits using the Conventional Commits format (type(scope): summary). Use when Codex needs to stage changes, craft commit messages, and record completed work in a Git repository.
| name | todo-json-manager |
| description | Manage project task lists stored in to-do.json and to-do.schema.json, including bootstrapping a backlog, selecting the highest priority task with jq, and updating task statuses. Use when Codex needs to read or update a JSON task list. |
Maintain the project task list in to-do.json using the schema in to-do.schema.json.
Required: schema_version, source_files, tasks.
source_files: array of relative paths to ground-truth docs (PROJECT.md, SPECS.md, etc.).
Required: id, title, priority (1-5), status (todo|doing|blocked|done).
Optional: details, steps, blockers, tags, files, depends_on, created_at, updated_at.
to-do.schema.json if present and follow it strictly.source_files and treat them as ground truth.jq to inspect tasks and identify the next task.
id.updated_at, and add relevant files or details.blockers entries.to-do.json formatted with 2-space indentation.jq '.tasks |= map(if .id=="T001" then .status="doing" else . end)' to-do.json > /tmp/to-do.json && mv /tmp/to-do.json to-do.json