Daily flow

This is the cross-tool flow that the toolkit is designed around. Use it as a template, not a script.

Morning

hop pull --all      # sync every tracked repo
tu                  # check yesterday's cost
idea list           # what's on the docket today

Pick a change

idea list --tag bug
# [a7q2] flaky timezone test in user-profile.tsx

wt create flaky-tz-test --from-idea a7q2
# new worktree at ../<repo>.worktrees/flaky-tz-test/
# fab change folder pre-created via the worktree init script

Drive the change with fab-kit

cd ../<repo>.worktrees/flaky-tz-test
rk riff --skill /fab-fff       # spawns Claude Code in this worktree, runs the pipeline

/fab-fff runs intake → spec → apply → review → hydrate → ship. You watch in rk’s browser dashboard; intervene only at gates.

Review the PR

gh pr view --web                    # open the PR
# leave comments yourself, or let Copilot review

# back in the worktree:
rk riff --skill /git-pr-review     # triages and fixes review comments

End of day

hop status --all     # show dirty repos
tu                   # today's spend
wt list --stale      # worktrees idle >7 days

Variants

• Multiple changes in parallel: wt create more worktrees; rk riff agents in each. The dashboard is the cross-pane view.
• Long-running change: when the spec stage produces a lot of [NEEDS CLARIFICATION] markers, run /fab-clarify between turns and answer them in batches.
• Cost-conscious mode: tu --watch in a side pane keeps the running cost visible.