apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Consolidate the project's auto memory in place (merge, correct, prune, re-index), then offer to clean up .turbo/. Use when the user asks to \"dream\", \"tidy memory\", or \"clean up stale notes\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill dream --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill dream -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill dream -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill dream -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill dream -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill dream -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill dream -a windsurf -y
name: dream description: "Consolidate the project's auto memory in place (merge, correct, prune, re-index), then offer to clean up .turbo/. Use when the user asks to \"dream\", \"tidy memory\", or \"clean up stale notes\"."
Consolidate this project's auto memory, then clear out what `.turbo/` no longer needs.
Text passed with the invocation steers the memory pass: what to look for and how to organize the notes. Every note is still read, and Step 3's conditions for deleting a note hold regardless.
Use the auto-memory directory the system prompt names. When it names none, an effective `autoMemoryDirectory` setting gives the location. Otherwise the directory is `<Claude config home>/projects/<encoded project root>/memory/`. The config home is `CLAUDE_CONFIG_DIR` when set and `~/.claude` otherwise. The key replaces every character outside `A-Za-z0-9` with `-`, and long keys may be truncated and hashed.
List the directory, then read `MEMORY.md` and every note with the Read tool. When the directory does not exist or holds no notes, say so and continue with Step 4.
Judge each statement in every note, and in every entry `MEMORY.md` holds in full rather than as a pointer to a note, by its kind:
Search the session transcripts only to settle which of two notes that contradict each other holds. Claude Code writes them to `<Claude config home>/projects/<key>/<session-id>.jsonl`. A session started in a subdirectory uses its own key, so match the encoded project root as a prefix. An `autoMemoryDirectory` setting does not move them. Search the transcripts modified after the older of the two notes for a narrow term, and output a short window around each match rather than the whole line, since one line can hold an entire tool result.
The step is done when every statement carries one of three verdicts: confirmed, contradicted with the evidence named, or unverifiable.
Apply these changes without asking, following the memory conventions from the system prompt:
Before the first edit this step makes to a note, and before deleting one, output its path and its full original text. Output each line of `MEMORY.md` before changing or removing it. Leave every file that is not a note or the index untouched.
When a write or a deletion is refused, continue with the rest and carry what is left to do into Step 5.
Resolve the repo root with `git rev-parse --show-toplevel`, except inside a linked worktree — where `git rev-parse --git-dir` differs from `--git-common-dir` — in which case use the parent of the common dir. Outside a git repository, use the working directory. When that root has no `.turbo/` directory, continue with Step 5.
List the top-level entries of `.turbo/` with one command that prints one line per entry: its size and the date of its newest file. Say what each holds from its name and, for a file, its heading. Read the frontmatter `status:` of every plan with one search.
Recommend deleting or keeping each entry by its kind:
Where a directory holds items with different recommendations, list the ones recommended for deletion together as one entry and the rest as another.
Output a numbered table of the entries with size, the date of the newest file, what each holds, and the recommendation.
Then use `AskUserQuestion`, one question per entry recommended for deletion, in number order, filling each call to its four-question limit:
After each call, delete the entries the user chose to delete. When an answer asks a question or gives an instruction in place of a choice, act on it, then ask about that entry again when delete or keep
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.