note-improvement

# 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`, or `plan` — see criteria below - **Category**: One of `refactor`, `performance`, `reliability`, `readability`, `testing`, `docs`, `dx` (developer experience), or `feature` - **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 `AskUserQuestion` 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 does...