Daily feedback on a goal is something you rarely get outside of a formal review. I recently created a daily reflection routine over my own chat history to help me identify instances where I was over-explaining before getting to the next step. It also reminded me of any open threads to reply to before I signed off for the day. Rather than having this bubble up through feedback at review time, the daily accountability helped keep me on track.
That routine wasn't an experiment for its own sake. In my 2025 summary blog post, I predicted "the challenge won't be any single capability but orchestrating skills, sub-agents, MCP servers, and other capabilities together effectively." The same capabilities everyone points at a codebase work just as well pointed at your own habits and at the recurring work that never gets prioritized or falls off your desk.
Working with internal platforms, one of the most useful signals I get is "on the ground" feedback from development teams in support channels and forums. There was no question of the value, but keeping up with it was taking more of the day than I had to give. So I built a routine to collect trends across support threads and surface where friction was showing up. This included an app connector for the chat tool, a skill defining how to fetch and organize the results, and a set of markdown files as a simple state store for durable trends. This gave me a standing view of what developers are hitting, so the decisions I make about platform work start from their experience instead of my assumptions.
