file-todos

Create and manage markdown todos with YAML frontmatter in the todos/ directory.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/minhcopilot/antigravity --skill file-todos-minhcopilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/minhcopilot/antigravity/tree/main/skills/file-todos
Command: npx skills add https://github.com/minhcopilot/antigravity --skill file-todos-minhcopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a lightweight, file-based todo system that lives in a todos/ directory. By using markdown files with YAML frontmatter, teams can track work items, their status, and dependencies in a centralized, human-readable format, reducing context-switching and lost tasks.

Core Features & Use Cases

  • Create new todos with a consistent file name and initial status (pending).
  • Move items through a simple status lifecycle (pending → ready → complete) and manage blockers via dependencies.
  • Resolve work items and log activity for traceability, review, and progress reporting.

Quick Start

Use the file-todos skill to create and manage todos inside the todos/ directory by following the naming conventions and lifecycle described in this guide.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I track project todos using markdown files in a repository?

You can track project todos by storing markdown files with YAML frontmatter in a todos/ directory. This file-based system manages task status and dependencies in a human-readable format, keeping work items centralized and reducing context-switching within your repository.

What is the status lifecycle for file-based todo management in a local script workflow?

The status lifecycle for file-based todos transitions tasks from pending to ready, and finally to complete. Local scripts enforce this workflow by parsing YAML frontmatter, managing dependencies for blockers, and logging activity to ensure progress traceability.

How do I automate todo creation and generate unique IDs for markdown task files?

Automating todo creation and ID generation relies on script-driven workflows that parse YAML frontmatter. Local scripts enforce consistent file naming conventions, assign an initial pending status, and generate unique traceable IDs for each markdown task file in the todos/ directory.

Do I need a database to manage project status tracking and dependencies for repository tasks?

You do not need a database to manage project status tracking and dependencies for repository tasks. A lightweight, file-based system using markdown files with YAML frontmatter tracks work items and manages blockers locally through script-driven automation without external database dependencies.

How do I log activity and resolution history for markdown todos in a local workflow?

Logging activity and resolution history for markdown todos is handled by the local script-driven workflow. As items move through the status lifecycle to complete, scripts log the activity to provide traceability, review capabilities, and progress reporting for all managed work items.