GoKawiilConcept proposes storing software tasks as Markdown files in Git repositories
A workflow called 'Tasks as Code' suggests replacing external trackers like Jira or Redmine with Markdown task files stored directly in a code repository's /docs-style folder. The approach extends the existing 'Docs as Code' practice, letting AI coding agents read tasks, code and documentation in one place and record updates through ordinary Git commits. It is linked to Spec-Driven Development, where Markdown specifications define intended behavior before an agent implements it.
GoKawiil's interpretation of the reporting above, not reported fact.
Keeping tasks in the same repository as code could let AI coding agents plan and execute work without switching between external systems, potentially streamlining agent-driven development. This suggests a broader shift toward treating all project artifacts—code, docs, and tasks—as version-controlled text, though teams reliant on dedicated project-management tools may need new interfaces to stay involved without using the command line.
- 'Tasks as Code' proposes storing tasks as Markdown files in Git instead of tools like Jira.
- It builds on the established 'Docs as Code' practice of keeping documentation in the repository.
- The concept ties into Spec-Driven Development, where Markdown specs guide AI agent implementation.
Source: typemill.net — Sebastian Schürmanns, 2026-10-26
Published there as: “Tasks as Code: Move Your Tickets into the Repository”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.