note-improvement

Log out-of-scope improvement ideas into a project-specific `.turbo/improvements.md` file.

399|31|Updated Mar 11, 2026

Search Tags:#code quality #refactoring #logging #developer experience #backlog #improvement

Ready to run

npx skills add https://github.com/tobihagemann/turbo --skill note-improvement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: note-improvement
Source: https://github.com/tobihagemann/turbo/tree/main/skills/note-improvement
Command: npx skills add https://github.com/tobihagemann/turbo --skill note-improvement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents valuable improvement ideas discovered during development from being lost by providing a structured way to log them for later consideration.

Core Features & Use Cases

Capture Improvement Ideas: Records suggestions for refactoring, performance enhancements, bug fixes, or feature additions that are outside the current task's scope.
Organized Backlog: Appends notes to a project-level .turbo/improvements.md file, creating a centralized and searchable backlog.
Use Case: While working on a feature, you notice a section of code could be significantly more readable. Instead of getting sidetracked, you use this skill to quickly note the improvement, categorize it, and continue with your current task.

Quick Start

Note that the user interface could be improved by adding a dark mode option.

Frequently Asked Questions about note-improvement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I log out-of-scope code improvements without stopping my current development task?▼

You can log out-of-scope code improvements by capturing refactor, performance, or developer experience suggestions into a centralized `.turbo/improvements.md` file, categorizing them for later review without interrupting your active development session.

What is the best way to maintain a backlog of code quality and refactoring ideas during feature development?▼

Maintaining a backlog of code quality ideas involves appending categorized notes for bug fixes or refactoring opportunities to a project-specific markdown file, ensuring actionable suggestions are recorded and not lost during feature development.

Can I categorize developer experience improvement notes by type when logging them?▼

Yes, you can categorize developer experience improvement notes by type, such as refactor, performance, or bug fix, when logging them into the project backlog to ensure organized and searchable records.

Does this backlog logging approach require any specific external dependencies or project setup?▼

This approach requires no external dependencies, relying solely on a project-level `.turbo/improvements.md` file to capture and organize improvement opportunities within your existing development environment.

When should I avoid logging improvement ideas during a development session?▼

You should avoid logging improvement ideas if the suggestion is within the current task scope, as this tool is specifically designed to capture out-of-scope opportunities to prevent scope creep and context switching.