Where does the skill store active and completed tasks?

Active tasks are maintained in the 'todos/zh/active/' directory, and once marked as done or cancelled, they are automatically moved to the 'archive/' directory.

How are task IDs assigned by this skill?

The skill automatically scans the task directory to find the current maximum TASK-XXXX number and increments it by 1 to ensure unique, continuous ID allocation.

What metadata is included in each task file?

Each task file includes YAML front-matter containing the unique ID, task type, current status, title, creation date, and author.

What is the 'Task as Code' philosophy?

It is a workflow where tasks are treated like source code—versioned, persistent, and stored directly in the repository rather than just in ephemeral chat histories or external tools.

Task as Code Expert

Name: Task as Code Expert
Author: IndenScale

byIndenScale

•

Productivity & Workflow

Manages project tasks through a structured 'Task as Code' workflow by maintaining persistent Markdown-based todo files.

About

The Task Expert skill implements a robust 'Task as Code' philosophy, ensuring that development progress remains persistent and organized beyond ephemeral chat sessions. By automating the creation, tracking, and archiving of Markdown task files within the repository, it prevents technical debt and ensures every requirement or bug is documented with a unique ID, metadata, and a clear execution plan. This skill is essential for developers who want to bridge the gap between fluid AI conversations and structured, version-controlled project management.

Key Features

Automated task ID allocation and incremental numbering
Enforcement of documentation standards to prevent 'hidden logic'
Integrated workflow tracking with objectives and technical notes
Standardized Markdown templates with metadata front-matter
Systematic task archiving for completed or cancelled items
5 GitHub stars

Use Cases

Automating the organization of project backlogs and archives within a repository
Maintaining a transparent 'Source of Truth' for long-running development tasks
Tracking feature implementation and bug fixes in a persistent file-based system

About

Key Features

Automated task ID allocation and incremental numbering
Enforcement of documentation standards to prevent 'hidden logic'
Integrated workflow tracking with objectives and technical notes
Standardized Markdown templates with metadata front-matter
Systematic task archiving for completed or cancelled items
5 GitHub stars

Use Cases

Automating the organization of project backlogs and archives within a repository
Maintaining a transparent 'Source of Truth' for long-running development tasks
Tracking feature implementation and bug fixes in a persistent file-based system