dd-later-tracking

Persists deferred work items to a project-level LATER.md file with deduplication.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill dd-later-tracking-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-later-tracking
Source: https://github.com/marcocpt/trae_skills/tree/main/dd-later-tracking
Command: npx skills add https://github.com/marcocpt/trae_skills --skill dd-later-tracking-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deferred tasks mentioned in conversation ("later", "next version", "skip for now") vanish when a session ends because session-level todo lists are not persisted. This Skill records cross-session deferred items in a project-root file so nothing is silently lost. ## Core Features & Use Cases - Persistent Deferred-Item Log: Writes deferred items to /docs/AI/LATER.md in the project root, surviving across sessions. - Two-Step Deduplication: Greps existing entries for candidates, then uses a subagent to judge whether a new item is the same issue (modify) or independent (append). - Structured Line Format: Each entry follows - [ ] LATER1. description #module-tag with an 80-character limit and completion marking via - [x]. - Use Case: During debugging you notice an unrelated token-expiry bug. Instead of losing it or polluting the current todo list, record it in LATER.md and revisit it in a future session. ## Quick Start When the user says "let's handle this later", read /docs/AI/LATER.md, deduplicate against existing entries, and append or update a single-line LATER item with a module tag.

Frequently Asked Questions about dd-later-tracking

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

FAQPage Schema
How do I track deferred tasks across AI chat sessions?

Record deferred items in a persistent project file like /docs/AI/LATER.md rather than session-level todo lists. Session todo tools lose state when the conversation ends, while a markdown file in the project root survives across sessions.

What is the difference between TodoWrite and a LATER.md file?

TodoWrite tracks tasks within the current session and is discarded when the session ends. LATER.md persists deferred items in the project root for future sessions, making it the correct choice when a user explicitly postpones work.

How do I avoid duplicate entries in a deferred-items list?

Read the existing file and grep for keywords from the new item to find candidate matches, then judge whether they describe the same underlying issue. Same issue means modify the existing entry; related but independent issues get a new line.

When should I not use a LATER tracking file?

Do not use it for tasks that will be handled within the current session, issues the user explicitly wants fixed immediately, or items already marked complete. Those belong in session-level task tracking or direct action.

What format should deferred task entries follow?

Use a single line per item: a checkbox, a numbered LATER prefix, a description under 80 characters, and module or feature-area tags. Avoid type-based tags like #bug and never expand entries into paragraphs.