Standardize Todo task files with directory structure and validation rules.
npx skills add https://github.com/thlandgraf/cc-marketplace --skill todo-format
Please help me install this Agent Skill. Skill: Todo Format Source: https://github.com/thlandgraf/cc-marketplace/tree/main/plugins/todo/skills/todo-format Command: npx skills add https://github.com/thlandgraf/cc-marketplace --skill todo-format
This skill clarifies the standardized Todo task file format, directory structure, and naming conventions to streamline task organization and collaboration.
Create a new task file in todo/open following the 3-digit ID and slug format and begin updating its status as you work.
High-intent search queries and answers about installing and using this skill.
A standardized markdown todo workflow organizes tasks into open, wip, and done directories. This directory structure supports full task tracking, branching, and review workflows by enforcing consistent status flow and file validation rules.
To create a new task file, place a markdown document in the todo/open directory using a 3-digit ID and slug naming convention. This standardizes task identification and ensures files pass structural validation when moving to wip or done.
The todo status flow works by moving task files between open, wip, and done directories. As you start work, move the file to wip, and upon completion, move it to done, ensuring consistent task tracking and reproducible workflows across the team.
Yes, you can use Git- and command-based interactions to manage the todo task workflow. The format specifies integration practices that support branching, task tracking, and review processes, ensuring consistent and reproducible task management within team environments.
No special dependencies are required to implement this todo file format. It relies on standard markdown files and directory structures, allowing you to enforce task management validation rules and naming conventions without installing additional software.
Validation rules for the todo markdown format check file naming conventions, 3-digit IDs, slugs, and required header fields. These rules ensure consistent task file structure and reliable status flow across open, wip, and done workflow stages.
MINT-IACapture conversation tasks into markdown todo files with YAML frontmatter.
aberrantCodeParse markdown task files for completion markers and update project plans.
snake-dev-teamOrganize project files and directories using predefined naming and markdown standards.
lenadlmAutomate Kanban workflow orchestration by decomposing tasks and assigning specialists.
