dev10x-park-todo

Store deferred work items as TODO/FIXME comments or in a .claude/TODO.md file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-park-todo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev10x-park-todo
Source: https://github.com/wooyek/dev10x-ai/tree/main/codex-skills/dev10x-park-todo
Command: npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-park-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the loss of deferred tasks by saving them to persistent storage, ensuring they are rediscovered in the correct context when working on nearby code or starting a new session in the same project.

Core Features & Use Cases

  • Inline Code Comments: Add TODO or FIXME comments directly into source code files for actionable items or known issues.
  • Project TODO File: Append deferred items to a .claude/TODO.md file in the repository root for broader project tracking.
  • Contextual Rediscovery: Automatically detects current date, branch, and repository root to maintain context.
  • Use Case: When you need to pause work on a feature or remember a bug fix, use this skill to log it either as a comment in the relevant code file or in a central project TODO list, so it's not forgotten.

Quick Start

Use dev10x:park-todo to add a TODO comment to the current file about configuring the webhook secret.

Frequently Asked Questions about dev10x-park-todo

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

FAQPage Schema
How do I persist TODO and FIXME comments so they aren't lost between coding sessions?

To persist TODO and FIXME comments, this skill stores deferred work items either as inline code comments or within a project-level `.claude/TODO.md` file. This ensures tasks are rediscovered in the correct context when working nearby.

What is the best way to track deferred tasks within a specific git branch?

Tracking deferred tasks within a git branch is handled by automatically gathering context like the current date and repository root. It logs items directly in code or a central project file for accurate contextual rediscovery.

Can I log project-level deferral items separately from inline code comments?

Yes, you can log project-level deferral items separately by appending them to the `.claude/TODO.md` file in the repository root. This keeps broader project tracking distinct from inline code comments.

How do I add a TODO comment to a source code file for a known issue?

You add a TODO comment to a source code file by using this skill to insert actionable items or known issues directly into the code. It automatically captures the current date and branch for accurate logging.

When should I use a project TODO file instead of inline code comments?

You should use a project TODO file for broader project tracking of deferred work items, while inline code comments suit actionable items tied directly to specific source code. Both prevent tasks from being forgotten.