todo-manage

Organize project TODO.md files with phased task breakdowns and cleanup.

12|2|Updated May 29, 2025
One-click install
npx skills add https://github.com/sorryhyun/DiPeO --skill todo-manage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-manage
Source: https://github.com/sorryhyun/DiPeO/tree/main/.claude/skills/todo-manage
Command: npx skills add https://github.com/sorryhyun/DiPeO --skill todo-manage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing project tasks, especially for complex features, can quickly become disorganized, leading to missed deadlines, unclear priorities, and wasted effort. This skill automates the creation, organization, and maintenance of a comprehensive TODO.md list, ensuring clarity and efficient project execution.

Core Features & Use Cases

  • Phase-Based Planning: Automatically breaks down complex projects into 3-5 logical phases with detailed, actionable tasks, effort estimates, affected files, and risk assessments, providing an immediate, structured plan.
  • Task Tracking & Updates: Facilitates marking tasks complete, updating progress notes, and noting blockers or dependencies, ensuring the TODO.md always reflects the current project state.
  • Automated Cleanup: Regularly removes completed or stale tasks, consolidating duplicates, and keeping the project's TODO.md concise, focused, and relevant.
  • Use Case: When starting a new feature like "MCP SDK Migration," simply describe the goal. This skill will generate a structured TODO.md with phases, estimated efforts, affected files, and potential risks, providing an immediate, actionable plan for development and clear communication of progress.

Quick Start

Quick Format Structure for a new project:

# DiPeO Project Todos

## [Project Name] (Priority Level)

Goal: One-sentence description

Context: Why this work is needed

Target: End state

### Phase 1: [Phase Name] ([Estimated Effort])

[Phase description]

- [ ] [Action verb task description]

- Estimated effort: Medium (2-3 hours)

- Files: path/to/file.py

Frequently Asked Questions about todo-manage

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

FAQPage Schema
How do I organize a complex project into phases with actionable tasks?

Phase-based project organization breaks complex work into 3-5 logical phases, each with detailed tasks including action verbs, effort estimates, affected files, and acceptance criteria. This Skill automatically generates a structured TODO.md that transforms a high-level goal into an immediate, executable plan with clear milestones and dependencies.

What should a comprehensive project TODO list include?

A comprehensive TODO list contains phase structure, detailed tasks with effort estimates, files affected, acceptance criteria, risk assessments, mitigation strategies, blockers, and progress notes. This format ensures nothing falls through the cracks and keeps stakeholders aligned on project state and priorities.

How do I track progress and keep my TODO.md current?

Mark tasks complete, update progress notes, and flag blockers or dependencies directly in your TODO.md. This Skill maintains the file by automating cleanup of completed tasks after defined delays and consolidating duplicates, so your TODO always reflects the current project state without manual maintenance.

Can I use markdown-based task planning for feature development?

Yes. Markdown TODO lists work well for feature development when structured with phases, effort breakdowns, and risk assessments. This Skill enforces a comprehensive markdown format that scales from simple task lists to complex multi-phase projects, keeping documentation in version control alongside your code.

When should I use automated task cleanup instead of manual updates?

Automated cleanup prevents stale tasks from cluttering your TODO.md and reduces maintenance overhead as projects grow. Schedule periodic cleanup to remove completed items after a defined delay, keeping your project plan focused on active work rather than historical records.

What's the best way to break down a large feature into manageable tasks?

Break large features into 3-5 phases, then decompose each phase into specific tasks with action verbs, effort estimates, affected files, and acceptance criteria. Include risk assessments and potential blockers upfront so the team understands dependencies and can plan parallel work effectively.