tl-devlog

Create and append structured DEVLOG.md entries with category and rationale.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-devlog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tl-devlog
Source: https://github.com/toddlevy/tl-agent-skills/tree/main/plugins/tl-devlog/skills/tl-devlog
Command: npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-devlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a durable, centralized log of architectural decisions, milestones, incidents, and insights to preserve context across sessions.

Core Features & Use Cases

  • Create and append a DEVLOG.md entry for decisions, milestones, incidents, and insights.
  • Support proactive prompts and an approval workflow before persisting entries.
  • Store entries in reverse-chronological order in the repository root DEVLOG.md, with category tagging and rationale.

Quick Start

Tell me to log a decision by saying "log this" or "devlog" and I will draft and append a DEVLOG.md entry.

Frequently Asked Questions about tl-devlog

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

FAQPage Schema
How do I maintain a development log for architectural decisions and milestones across sessions?▼

To maintain a development log, you can append structured entries to a DEVLOG.md file. This captures architectural decisions, milestones, and incidents to preserve historical context across development sessions.

What is the best way to track project incidents and decision rationales in a repository?▼

Tracking project incidents and decision rationales is done by appending entries to a root DEVLOG.md file. Entries are stored in reverse-chronological order with category tagging and required rationale text.

How do I create a DEVLOG entry and commit it to my repository?▼

To create a DEVLOG entry, prompt the system to log a decision. It drafts an entry requiring a category, title, and rationale, then uses an approval workflow before persisting the commit to DEVLOG.md.

Does this devlog tracking approach require any specific dependencies or components?▼

This devlog tracking approach requires no specific dependencies or components. It operates independently to generate frontmatter-driven entries and requires only user approval to commit to the repository.

Can I use this for proactive milestone logging at natural pause points?▼

Yes, you can use this for proactive milestone logging at natural pause points. It supports proactive prompts to capture important events and insights during software development workflows.