skills.rest
compojoom
compojoomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

file-todos

Create and manage markdown todos with YAML frontmatter for code-review workflows.

Updated Aug 23, 2026
Search Tags:#workflow#markdown#todo#triage#code-review#slash-commands#work-log
One-click install
npx skills add https://github.com/compojoom/safe-engineering-plugin --skill file-todos-compojoom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/compojoom/safe-engineering-plugin/tree/main/plugins/safe-engineering/skills/file-todos
Command: npx skills add https://github.com/compojoom/safe-engineering-plugin --skill file-todos-compojoom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The File-based Todo Tracking Skill reduces chaos in code-review workflows by providing a lightweight, human-readable system to capture, triage, and manage work items as markdown files in the todos/ directory.

Core Features & Use Cases

  • Create new todos from findings or feedback by generating markdown files using a consistent naming convention (e.g., 001-pending-p1-description.md).
  • Manage todo lifecycle from pending to ready to complete with status-aware frontmatter, and maintain a detailed work log.
  • Triaging and dependency management to coordinate parallel work and ensure blockers are resolved before starting.
  • Integrates with slash commands and code-review processes to surface actionable items in the IDE or CI pipeline.

Quick Start

Use the skill to create a new todo in the todos/ directory following the template. For example, create todos/001-pending-p2-improve-docs.md and fill in the required sections, then triage to ready or complete as work progresses.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I track code-review feedback using markdown files?▼

Track code-review feedback by generating markdown files in a todos/ directory using YAML frontmatter. This file-based todo system captures review findings and triages work items with status, priority, and dependency metadata.

What is the best way to manage code-review triage dependencies in a local workflow?▼

Manage code-review triage dependencies by adding dependency fields to markdown todo files. This coordinates parallel work and ensures blockers are resolved before starting, maintaining a detailed work log of decisions.

Can I use slash commands to create todos from pull request findings?▼

Yes, slash commands integrate with code-review processes to surface actionable items in the IDE or CI pipeline. This creates new todo markdown files from findings using a consistent naming convention.

How do I structure a markdown todo template for software development workflows?▼

Structure markdown todo templates with YAML frontmatter containing status, priority, and dependencies. Name files using conventions like 001-pending-p1-description.md to track the lifecycle from pending to complete.

Does this file-based todo system require external dependencies to manage work logs?▼

No, this file-based todo system has zero external dependencies. It uses markdown files with YAML frontmatter and optional assets to document decisions and maintain work logs without requiring additional packages.

Related Skills

Explore More Software Engineering Skills→
hackefellerhackefeller
1

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Official
Intermediate
sammyjoycesammyjoyce

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Community
Advanced
ybbms777ybbms777
1

todo-resolve

Resolve batch-approved todos in parallel and capture lessons via ce:compound.

Community
Advanced
barkleesandersbarkleesanders
5

file-todos

Create and track file-based todos for code review feedback and technical debt.

Community
Intermediate