Ryuu's Skills

The Loop

How a batch of work moves from a survey to merged pull requests.

Start with /plans to see what is ready. The plans skill owns the loop.

CommandWhat it does
/plansPrints the frontier: ready rows by priority, then blocked rows with their blockers or the red check that stopped them, REVIEW rows (PR open) and DOING rows (a thread is on it). It reads no plan bodies.
/plans new [hint]Surveys the project, asks where the work lands, and writes the batch it finds. Without a hint, it surveys the whole project. It does not implement or edit code.
/plans do <id>Checks the destination, cuts the plan's branch, probes the repo, routes to a playbook, verifies the work, and hands it back. Without an id, /plans do takes the next ready row.
/plans waveRuns the same sweep as /plans close with no id first, then starts a T3 Code thread running /plans do <id> for each ready row whose probe files overlap no other launching row, and names each held row with the file it shares. Elsewhere it prints the /plans do prompts.
/plans resumeSends each stalled DOING thread in T3 Code one message naming why it stopped, a usage limit, a restart, or idle time, and asking it to carry on. PLANS_RESUME_EVERY schedules it.
/plans threads resumeDoes the same for each stalled ad hoc thread, found through its PR, in any repository. THREADS_RESUME_EVERY schedules it.
/plans review <id>Reads the review and fixes or dismisses each finding. It replies only in threads of an active reviewer extension and drafts the rest.
/plans close <id>Writes what landed, marks the row DONE or DROPPED, moves the plan into done/, and settles the thread where the harness supports it.
/plans closeCloses each DOING or REVIEW row whose PR merged once its thread has finished, removes each closed row's /tmp/plans-<id>/ scratch that no other row holds, settles its thread where the harness supports it, reaps the simulators, emulators, containers and dev servers closed plans left through skills reap, and last releases each closed plan's checkout that nothing still works in through skills plans release. Rows it cannot close yet, and PRs closed without merging, are reported, never dropped. The thread you run it in stays open. PLANS_SWEEP_EVERY schedules it.

Hand Back

  • In hands-off mode, you review, commit, and open the PR.
  • In prs mode, the agent opens the PR or the next stack layer and babysits it through the reviewer round.

For a whole batch, follow Running a Batch.

One Thread per Plan

One thread works one plan in one checkout. To run several plans at once, give each its own worktree. The skills never create one themselves. Subagents and Codex arms work in the checkout they started in.

On this page