file-todos

Create and manage source-scoped file-todos with YAML frontmatter and status history.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune-plugin --skill file-todos-vinhnxv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/vinhnxv/rune-plugin/tree/main/plugins/rune/skills/file-todos
Command: npx skills add https://github.com/vinhnxv/rune-plugin --skill file-todos-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Structured file-based todo tracking for Rune workflows. Each todo is a markdown file with YAML frontmatter and lifecycle status. Source-aware templates adapt for review findings, work tasks, PR comments, tech debt, and audit findings. Session-scoped: todos live in tmp/{workflow}/{timestamp}/todos/, cleaned by /rune:rest. Use when creating, triaging, resolving, or querying todos from any Rune workflow.

Core Features & Use Cases

  • Per-source todos stored under the session tmp directory with per-source manifests to drive ordering, dependencies, and progress tracking.
  • Rich frontmatter including status, priority, dependencies, assignments, resolution, and a durable Status History for auditability.
  • Cross-workflow coordination via cross-source references and a modular manifest system to minimize LLM context and maximize determinism.

Quick Start

Create a new todo with /rune:file-todos create in your active workflow session.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I track workflow tasks and review findings using file-based todos?

Track workflow tasks using file-based todos by creating structured markdown files with YAML frontmatter. Each todo captures findings, plans work, and tracks resolutions using per-source manifests with status transitions and dependency graphs.

What is the best way to manage task dependencies in a code review workflow?

Manage task dependencies in a code review workflow using per-source manifests that enforce ordering and track progress. Cross-source references and a modular manifest system coordinate work across strive, appraise, audit, and mend workflows.

How do I create a structured todo with status history for audit findings?

Create a structured todo with status history by generating a markdown file with YAML frontmatter. The lifecycle enforces status transitions and records a durable Status History, ensuring auditability for audit findings and tech debt.

Does session-scoped todo tracking clean up temporary workflow files automatically?

Session-scoped todo tracking stores files in tmp/{workflow}/{timestamp}/todos/ and cleans them via the /rune:rest command. This ensures temporary workflow files are managed automatically without manual intervention.

Can I use per-source manifests to minimize LLM context during task triage?

Yes, per-source manifests minimize LLM context and maximize determinism during task triage. The modular manifest system isolates source-specific data, reducing context overhead while maintaining cross-workflow coordination.

When should I avoid using source-scoped file-todos for workflow management?

Avoid using source-scoped file-todos for workflow management if you need persistent storage outside the session tmp directory. Todos are session-scoped and cleaned by /rune:rest, making them unsuitable for permanent task tracking.