Shared definition of technical debt for the team
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Ask five engineers what counts as technical debt and you get five answers: ugly code, missing tests, an old framework, a product decision someone dislikes.
First tasks
- Ask three teammates for one example each of debt that slowed them down this month
- Ask the agent to draft a one-page definition from those examples
- List five things the team should not log as debt, such as bugs and feature requests
- Agree the wording at the next team meeting and link it from the README