Tasks as Code: Moving Task Tickets into the Code Repository as Markdown

A Typemill knowledge base article proposes the Tasks as Code approach: writing tasks and requirements as Markdown files and storing them in a Git repository, so that AI coding agents can read requirements and code in the same place. The article presents a five-step process: describe the task, analyze the requirements, generate an implementation plan, obtain human review and approval, then implement and write back a report. It also recommends splitting code, documentation, and tasks into three repositories, using .gitignore to isolate local clones. The author also mentions that interfaces supporting Git sync, such as Typemill, can let product managers and technical writers participate, while Git still handles version history.