implement-improvements

# Implement Improvements Validate improvements from `.turbo/improvements.md`, propose a specific working set based on the backlog's actual contents, and run one lane per session: direct, investigate, or plan. Mixing lanes in a single run tangles commits, so the skill processes exactly one lane each time. Entries outside the confirmed working set stay in the backlog for future runs. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Read the backlog 2. Validate and classify 3. Recommend, confirm, and prune stale 4. Run the chosen lane 5. Prune working-set entries from the backlog ## Step 1: Read the Backlog Read `.turbo/improvements.md`. If the file does not exist, there are no improvements to implement; stop. Parse all entries, extracting for each: - **Summary** (the `###` heading) - **Type** (`direct`, `investigate`, or `plan`; may be missing in older entries — `trivial` and `standard` are accepted as legacy aliases for `direct` and `plan`) - **Category** - **Where** (file paths or areas) - **Why** (rationale) - **Noted** (date) ## Step 2: Validate and Classify Improvements can go stale: files get renamed, code gets refactored, issues get fixed as side effects of other work. Before routing, validate each improvement and classify any entry missing a Type. ### Validate For each entry, verify whether the specific problem or opportunity described still exists. Do not rely on git log alone. Recent commits touching the same files do not ...