Put your tickets with your code

One of the core ideas of my skills repo is that all the tickets - the type that would normally get added to Jira or GitHub Issues - now live in your git repo as simple markdown files. This is done for a couple of reasons:

1. The context that each ticket contains is easily available to your coding agent.
2. The whole workflow is based around creating/refining/completing tickets, the locality makes it simple for the agent to do.

What is really great about this approach is that it makes it super simple for your coding agent to work out what code changes go with which feature, and why that feature was added. If you ever ask your agent to change some existing code, your agent will be able to trace it back to the original ticket and then be able to understand at a product level why the code exists and what the implications might be for changing it.

You have put in all this work in shaping and refining your tickets - all this valuable context. Why not fully capitalise on it by putting it with your code? In the age of AI I think we are all missing a trick here by not doing so.