A MyThingsLab My[X] tool: curate a TODO.md from live
signals — a repo's open GitHub issues plus MyPlanner's latest plan — and
open a PR. It's the prospective counterpart to MyReporter's retrospective digest:
a durable, checked-in "what to do next", grouped Now / Next / Later.
Curates either one repo's own TODO.md or an org-wide roll-up.
# One repo's own TODO.md, from its open issues (+ MyPlanner's plan if present).
mytodo repo --repo MyThingsLab/my-todo --source .
# An org-wide roll-up, aggregating every repo's open issues into one board.
mytodo org --org MyThingsLab --into MyThingsLab/fleet-dispatch --source ../fleet-dispatch
# Preview without opening a PR; or let a model do the prioritising:
mytodo repo --repo MyThingsLab/my-todo --no-pr
mytodo repo --repo MyThingsLab/my-todo --engine claude-cliPrioritising is the tool's single, optional Engine call. Against the default
--engine noop (zero tokens) issues are grouped deterministically by label
(safety/bug → Now, core-contract/needs-decision → Next, rest → Later);
--engine claude-cli lets a model do the triage, degrading to that same grouping
on any empty reply. MyPlanner's plan is read from its ledger on disk (the same
seam MyOrchestrator uses) — a next horizon surfaces as a Planner focus note
and a "pause new tools" flag as a banner. No plan ⇒ issues only, unchanged.
my-todo reads issues and writes one TODO.md PR — it never merges and never
mutates issues. Re-running with no changes is a no-op (skipped).
python -m venv .venv && source .venv/bin/activate
pip install -e ../my-things-core -e ".[dev]"
pytestSee CLAUDE.md for the tool's seams and HARNESS.md
for the inherited build rules.
MIT — see LICENSE.