Docs As Code

Concept 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.