Todos Babysit

Babysit Todos

Codex host guard

Before any other action, check whether CODEX_THREAD_ID is set. If it is, stop before reading or changing todo state, creating worktrees or PRs, dispatching implementation, or sending notifications. This release supports Todos Babysit only on Claude Code; tell the user its Codex engine is not shipped yet and to run the workflow there instead.

Periodic scanner for backlog and in-progress todos. Cross-references with GitHub PR status, reviews unhandled items, notifies the user, and auto-implements on approval.

Config Discovery

Resolve todo directory paths and optional Discord config. Source the config helpers first:

# --- solopreneur config helpers (sourced from shared/config.sh) ---
# One real shell file, so no harness rewrites the helpers on the way to the
# shell. Claude Code replaces the ${CLAUDE_SKILL_DIR} token below when it loads
# this body; Codex does not. It is SINGLE-quoted on purpose — it is a load-time
# token, not an environment variable, and letting the shell expand the name
# would source whatever an inherited value happened to point at. Unreplaced, it
# is not a directory, so substitute the absolute path of the directory holding
# THIS SKILL.md — every harness states that path to the model.
SOLO_SKILL_DIR='${CLAUDE_SKILL_DIR}'
[ -d "$SOLO_SKILL_DIR" ] || SOLO_SKILL_DIR="<absolute path of the directory holding this SKILL.md>"
SOLO_CONFIG_SH="$SOLO_SKILL_DIR/../../shared/config.sh"
# Three candidates, one contract. Inside the plugin the helpers sit at ../../shared/;
# authoring against this repo reaches them under src/solopreneur/shared/; and a
# skill republished on its own — any flattened skills directory — carries them
# at scripts/config.sh instead, because shared/ is a sibling of skills/ and does
# not travel with a per-skill copy. Try each in order, then STOP. Sourcing a
# file that is not there does not halt the shell: every helper stays undefined,
# every config read returns empty, and the 2026-08-11 A2 run showed where that
# leads — the model "rescued" it with a repo-relative path, which resolves only
# when the repo under review happens to be this plugin's own source repo.
# Canonical authoring keeps non-skill source under src/.
[ -f "$SOLO_CONFIG_SH" ] || SOLO_CONFIG_SH="$SOLO_SKILL_DIR/../../../src/solopreneur/shared/config.sh"
[ -f "$SOLO_CONFIG_SH" ] || SOLO_CONFIG_SH="$SOLO_SKILL_DIR/scripts/config.sh"
[ -f "$SOLO_CONFIG_SH" ] || { echo "HALT: solopreneur config helpers not found under $SOLO_SKILL_DIR — stop here, do not improvise a path"; exit 1; }
source "$SOLO_CONFIG_SH"
# --- end solopreneur config helpers ---

1. Check plugin config:

   read_solopreneur_config todos
   read_solopreneur_config discord

2. If no todos config — run the same directory discovery as /todos-cleanup: scan project for todo directories, confirm with user, save to config.

3. Discord availability — auto-detect, no user prompt needed:

   # Check for Discord bot token
   if [ -f ~/.claude/channels/discord/.env ]; then
     source ~/.claude/channels/discord/.env
   fi
   
   # Also check plugin config for custom token path
   DISCORD_CFG=$(read_solopreneur_config discord)
   TOKEN_PATH=$(echo "${DISCORD_CFG:-{}}" | jq -r '.token_path // empty')
   if [ -n "$TOKEN_PATH" ] && [ -f "$TOKEN_PATH" ]; then
     source "$TOKEN_PATH"
   fi
   
   DISCORD_AVAILABLE=${DISCORD_BOT_TOKEN:+true}

   • Token found + discord.channel_id and discord.guild_id in config → use Discord
   • Token found but no channel/guild config → Discord available but not configured, ask user for channel ID on first run, save to config
   • No token → fallback to terminal output (all notifications print inline)

   Discord config format in ${CLAUDE_CONFIG_DIR:-~/.claude}/solopreneur.json:

   {
     "discord": {
       "channel_id": "123456789",
       "guild_id": "987654321",
       "token_path": "~/.claude/channels/discord/.env"
     }
   }

Notification Layer

All notifications go through a consistent interface. The skill decides the backend based on config discovery:

In terminal mode, after presenting all reviews, prompt the user for each item:

[todo-title]: go / later / done / skip?

Operating Modes

Babysit runs in one of two modes, detected automatically:

Auto mode safety principle: only take actions that are safe to do without human judgment. Anything that requires a judgment call → notify and stop.

Main Flow

Phase 1: Pull & Scan

1. git pull --rebase to get latest
2. List all .md files in both $BACKLOG and $DOING
3. Tag each item with its source directory (backlog or doing)
4. Fetch PR status:

   gh pr list --state open --json number,title,headRefName,url
   gh pr list --state closed --json number,title,headRefName,url,mergedAt --limit 20

   Filter closed PRs to last 2 days only (compare mergedAt).

Phase 2: Status Comparison

For each todo file, extract keywords from the filename (strip date prefix 2026-03-15- and type prefix feature-request- / bug-), then match against PR titles and branch names.

Classification rules differ by source directory:

$BACKLOG items

Detecting unchanged:

• Discord mode: todo's thread exists and has no user reply after the last bot message
• Terminal mode: skip detection (always re-present)

$DOING items

Key difference: $DOING items never get needs_review (they're already approved for work). A doing item with no PR is stale — possible causes: PR closed without merge, item manually moved, or branch deleted.

Phase 3: Confirmation Checkpoint

After classification, present a summary table. Behavior depends on operating mode.

Summary table (same for both modes):

📊 **Scan Results** ({YYYY-MM-DD HH:MM})

### Backlog ({N} items)
| Todo | Status | PR | Proposed Action |
|------|--------|----|-----------------|
| add-export.md | needs_review | — | Review |
| fix-sync.md | in_progress | #42 | Move to doing + maintain worktree |
| update-ui.md | merged | #38 | Move to done + cleanup |

### Doing ({N} items)
| Todo | Status | PR | Proposed Action |
|------|--------|----|-----------------|
| auth-flow.md | in_progress | #45 | Maintain worktree (rebase) |
| dark-mode.md | merged | #40 | Move to done + cleanup |
| old-feature.md | stale | — | ⚠️ No PR found |

Interactive mode: Post/print the table, then wait for user confirmation:

• yes / go → proceed with all proposed actions
• Override specific items (e.g., "skip add-export, move old-feature to done")
• stop → abort the scan
• Stale items: user picks per item (move to backlog / done / keep)

Auto mode: Post/print the table as a notification (no wait). Then auto-proceed with safe actions only:

• merged → auto-move to $DONE + cleanup
• in_progress → auto-maintain worktree
• needs_review → auto-review
• stale → notify only, do not move (requires human judgment)

Phase 4: Housekeeping

Execute non-review actions confirmed in Phase 3:

1. Merged items (both backlog and doing):

   • Clean up worktree if it exists:

     git worktree remove .worktrees/{slug} --force

   • Delete local branch:

     git branch -d {branch-name}

   • Move todo file to $DONE

2. In-progress backlog items → move to $DOING

3. In-progress items (both sources) — maintain worktrees:

   • Check for existing worktree:

     git worktree list | grep {branch-name}

   • Has worktree → rebase from main:

     cd .worktrees/{slug} && git fetch origin main && git rebase origin/main

   • No worktree → create one:

     git worktree add .worktrees/{slug} {branch-name}

   • Conflict handling:
     • Simple (< 3 files, clear resolution) → auto-resolve
     • Complex → notify user with conflict file list, wait for instructions
   • Push after successful rebase: git push --force-with-lease

4. Stale items → execute per user's instruction from Phase 3

Commit all file moves:

git add -A todos/
git commit -m "chore: babysit — move completed/stale todos"
git push

Phase 5: Review

For each needs_review backlog todo, invoke /todos-review {file-path}.

Extract from results: Destructiveness, Value, Effort, completion %, recommendation, and Readiness (Auto or Needs Discussion).

If many needs_review items (>10), prioritize:

1. High value + low destructiveness
2. Bug-type items
3. Remaining by date