kiln-todo

Manage TODO items in a .kiln/todos.md Markdown checklist.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-todo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiln-todo
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/kiln-todo
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage lightweight TODOs in .kiln/todos.md without going through the full spec pipeline.

Core Features & Use Cases

  • List open TODOs and view their order.
  • Add new TODO items with text, automatically timestamped.
  • Mark items as done and retain a history of completions.
  • Clear all completed items while preserving a clean TODO file.
  • File path context: .kiln/todos.md and a markdown checklist format.

Quick Start

Add a new TODO by issuing /kiln:kiln-todo <text> to append it to .kiln/todos.md.

Frequently Asked Questions about kiln-todo

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

FAQPage Schema
How do I manage lightweight TODOs in a local project without a complex task management setup?

You can manage lightweight TODOs by appending items to a centralized Markdown checklist file. This approach automates lightweight task tracking for local project workflows using a single file, allowing quick listing, adding, completing, and clearing of tasks.

How do I add a new TODO item to a Markdown checklist and track when it was created?

To add a TODO item, you issue an add command with your desired text. The system automatically appends the new item to the Markdown checklist as a single line and applies a timestamp to track when it was created.

Does this lightweight task tracking approach retain a history of completed items?

Yes, lightweight task tracking retains a history of completions. When you mark items as done, they are updated within the Markdown file, and you can clear all completed items later while preserving a clean checklist.

What is the best way to track local project tasks without going through a full spec pipeline?

The best way to track local project tasks without a full spec pipeline is using a centralized Markdown file. It supports quick listing, adding, completing, and clearing of TODOs, ensuring the file exists and maintaining a simple one item per line format.

Can I use a Markdown checklist to automate clearing completed tasks in my workflow?

Yes, you can use a Markdown checklist to automate clearing completed tasks. The system supports a clear command that removes all completed items from the file, preserving a clean TODO file for ongoing local project workflows.