Note Improvement
Productivitynote-improvementNote Improvement is an Agent Skill for productivity published in the tobihagemann/turbo repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something improvable during work that falls outside the current task's scope — briefly mention it to the user and offer to note it.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/tobihagemann/turbo/blob/HEAD/codex/skills/note-improvement/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/note-improvement, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Note Improvement
Capture improvement opportunities discovered during work so they don't get silently dropped. Appends to a project-level .turbo/improvements.md file that serves as a backlog of actionable ideas.
Step 1: Determine Project Root
Find the nearest .git directory or project root. The improvements file lives at .turbo/improvements.md relative to the project root.
Step 2: Identify the Improvement
Gather from context or $ARGUMENTS:
- What: One-line summary of the improvement
- Type: One of
direct,investigate, orplan— see criteria below - Category: One of
refactor,performance,reliability,readability,testing,docs,dx(developer experience), orfeature - Where: File path(s) and/or area of the codebase affected
- Why: Brief rationale — what's the benefit?
Type criteria
- direct — Clear scope and a known approach, ready to apply via
$implement. - investigate — A symptom that needs root-cause analysis first: unclear root cause, performance question, intermittent bug, "something feels off".
- plan — Everything else: the approach warrants writing down before implementing (multi-file refactor, test additions, feature work).
When the criteria above clearly select one value, use it. Otherwise, use request_user_input to confirm; default to plan if the user declines to choose.
Step 3: Append to File
Read .turbo/improvements.md if it exists. Create it with the header below if it doesn't.
File header (only when creating new):
# Improvements
Out-of-scope improvement opportunities captured during work sessions. Review periodically and pull items into active work when appropriate.
Entry format:
### <one-line summary>
- **Type**: <direct | investigate | plan>
- **Category**: <category>
- **Where**: `<file path or area>`
- **Why**: <brief rationale>
- **Noted**: <YYYY-MM-DD>
Append the new entry at the end of the file.
Step 4: Confirm
Tell the user the improvement was noted and where the file is.
Rules
- Deduplicate before appending: check for a similar entry and update it in place when one exists. When the existing entry predates the Type field, add a Type line while updating.
- When updating an existing entry tagged with the legacy values
trivialorstandard, rewrite the Type todirectorplanrespectively so the file converges on current vocabulary. - Keep entries concise — 3-5 lines max per entry. These are backlog items, not specs.
- Record only; leave action to the user, who decides when to address it.
- When the project has no
.turbo/directory, userequest_user_inputto confirm the location before creating one.