Docket is a software development ticket system that lives within your repository. I built the system from the ground up to support three primary mediums of access: by a human in the file system accessing Markdown files, by a human using the program's command line interface, and by agentic systems using a tailor fit MCP.

The concept behind the project is informed through the experience and learnings I've gathered through real development workflows under an evolving agentic SDLC. While the obvious primary benefit is not having to pay for a system like Jira or Linear, local ticket systems per repo help in other ways as well. For example, because the tickets are registered in the repository itself you have history of each version of the ticket. This matters for record keeping, but also provides any coding agents working on the system easy access to the decision chain that led to the program existing as it does at the time of query. Doing this provides context that would otherwise be assumed; a state that is not ideal when working with prediction matrixes. Further, among other values, the agentic system building the code can directly access the Docket MCP to propose new tickets based on emergent bugs or discussion with the human operator thereby utilizing the system as a two-way street that other remote ticket systems struggle to replicate.