rbrown101010/rileys-top-skills/todo

Todo

Point todo updates to this document:

<path-to-your-todo-list.md>

Use the emoji itself as the bullet:

• 🔵 Working Tasks / Working Videos
• 🟣 Working Videos
• 🟢 Done
• ⭘ Backlog / do later

Keep the document sections in this order:

1. Working Tasks
2. Working Videos
3. Backlog
4. Done
5. Videos Done

When updating the document, keep it simple. Do not add a status key, markdown bullets, checkboxes, or [x] marks. Add current project tasks under Working Tasks with 🔵, active video ideas under Working Videos with 🟣, completed normal work to Done, completed videos to Videos Done, and do-later items to Backlog.

Links

When adding or updating a todo item from an active Codex chat thread, append a clickable thread backlink at the end of that item's line.

Direct codex://threads/<thread-id> links are not reliably clickable in Markdown. Use a normal local web link labeled View Thread that redirects into the Codex deeplink:

[View Thread](http://127.0.0.1:8796/<thread-id>/)

Use the active thread's real thread ID in the URL only. Do not print or append the raw thread ID anywhere in the visible todo text. If the thread ID is not available in the chat context, ask the user to paste the copied Codex deeplink and extract the ID from codex://threads/<thread-id>. Do not invent a thread ID.

For each thread link, create or update this redirect page:

<path-to-your-thread-link-server>/<thread-id>/index.html

The redirect page should immediately send the browser to codex://threads/<thread-id> and include a fallback button labeled View Thread. Do not display the raw thread ID or the raw codex://threads/<thread-id> URL on the page.

If the local thread-link server is not already running, serve the thread-link-server folder on 127.0.0.1:8796. Prefer the existing LaunchAgent if present:

$HOME/Library/LaunchAgents/com.example.codex-thread-link.plist

When the todo item is about a document or artifact, include the artifact link inline before View Thread. This includes Google Docs, Google Drive folders/files, Notion pages, local HTML previews, GitHub PRs/issues, Vercel deployments, or any other source/output link created or used for the task. Do not leave the user hunting for the document later.