Tasks as Code: Move Your Tickets into the Repository
Summary
The article argues for moving tasks into the repository as Markdown files so AI coding agents can read, plan, and report within the same Git workflow. It ties the concept to Docs as Code and outlines a practical five-step process plus a three-repository setup, highlighting benefits like single source of truth, versioning, and easier collaboration. It also discusses interface options and privacy considerations when separating code, docs, and tasks.