Self-Improving Engineering

1. Log immediately — context is freshest right after the build breaks or the review lands 2. Include the error output — future agents need the exact error message to pattern-match 3. Record the environment — Node version, OS, CI runner matter for reproducibility 4. Link the PR or commit — makes root cause traceable 5. Suggest concrete fixes — not just "investigate" but "add index on users.email" 6. Categorize precisely — enables filtering by architecture_debt vs code_smell vs testing_gap 7. Promote aggressively — if it broke the build twice, it belongs in coding standards 8. Track recurrence — third time is a systemic issue, not a one-off