todo

Manage spec TODOs with markdown files and a central index.

27|2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/edochi/mdvs --skill todo-edochi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo
Source: https://github.com/edochi/mdvs/tree/main/.claude/skills/todo
Command: npx skills add https://github.com/edochi/mdvs --skill todo-edochi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec TODOs are scattered across documentation and require a standardized workflow to create, track, and resolve them using per-TODO markdown files and a central index.

Core Features & Use Cases

  • Create: add new TODOs as TODO-NNNN.md with a predictable frontmatter scaffold, including id, title, status, priority, created, depends_on, blocks.
  • Track: maintain an index.md with statuses, dates, and priorities to surface work at a glance.
  • Lifecycle and resolution: update statuses through the lifecycle (todo -> in-progress -> done) and add resolution notes or references when completed.

Quick Start

Create the next TODO by deriving the highest existing ID, then save a file named TODO-NNNN.md with the required frontmatter and update the index accordingly.

Frequently Asked Questions about todo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track spec TODOs across markdown documentation?

Track spec TODOs by creating per-TODO markdown files with standardized frontmatter and maintaining a central index. This workflow manages statuses, priorities, and dependencies to surface documentation work at a glance.

What frontmatter fields are required for a TODO markdown file?

Required frontmatter fields for a TODO markdown file include id, title, status, priority, created, depends_on, and blocks. This fixed template enforces consistent spec tracking across documentation.

How do I create a new TODO with sequential IDs?

Create a new TODO by deriving the highest existing ID, then save a file named TODO-NNNN.md with the required frontmatter scaffold. Update the central index to register the new entry.

What status transitions are supported for documentation TODOs?

Documentation TODOs support status transitions from todo to in-progress to done. Resolution notes or references can be added when a TODO is marked done to complete the lifecycle.

Can I manage TODO dependencies and blocking relationships in docs?

Manage TODO dependencies using the depends_on and blocks fields in the frontmatter. This convention tracks relationships between spec items to maintain execution order across documentation.

What's the best way to maintain a TODO index for spec documentation?

Maintain a TODO index by updating an index.md file with statuses, dates, and priorities for all spec items. This central index surfaces work at a glance and tracks lifecycle progress.