#vibecodinghacks
Have your coding agent keep a TODO and DONE list with numbered issues. This gives a clear overview of all issues and allows you to refer to them by number. Add this to your agent.md:
## TODO/DONE Tracking
Every project has `TODO.md` (open work) and `DONE.md` (completed work). After each commit, automatically:
1. Move completed items from `TODO.md` to `DONE.md` (with commit hash and date).
2. Add any new TODOs discovered during the work.
3. Show the user a brief summary of what changed.
### Issue Numbering (mandatory)
Every TODO and DONE item **must** have an issue number for tracking. Use project-specific prefixes.
Rules:
- **New TODOs**: Assign the next available number in the project's sequence.
- **Moving to DONE**: Keep the original issue number — never renumber.
- **Format**: `**PREFIX-NNN: Short title**` — e.g., `**CD-001: processGiftWrap swallows exceptions silently**`.
These instructions can probably be condensed it your agent.md is already bloated
Have your coding agent keep a TODO and DONE list with numbered issues. This gives a clear overview of all issues and allows you to refer to them by number. Add this to your agent.md:
## TODO/DONE Tracking
Every project has `TODO.md` (open work) and `DONE.md` (completed work). After each commit, automatically:
1. Move completed items from `TODO.md` to `DONE.md` (with commit hash and date).
2. Add any new TODOs discovered during the work.
3. Show the user a brief summary of what changed.
### Issue Numbering (mandatory)
Every TODO and DONE item **must** have an issue number for tracking. Use project-specific prefixes.
Rules:
- **New TODOs**: Assign the next available number in the project's sequence.
- **Moving to DONE**: Keep the original issue number — never renumber.
- **Format**: `**PREFIX-NNN: Short title**` — e.g., `**CD-001: processGiftWrap swallows exceptions silently**`.
These instructions can probably be condensed it your agent.md is already bloated
1❤️1🤙1