todo

Decompose a project into sprint-ready tasks with priorities, effort estimates, and dependencies.

Updated Feb 7, 2026

Search Tags:#planning #checklist #task breakdown #prioritization #agile #todo

Ready to run

npx skills add https://github.com/maggit/claude-workspace --skill todo-maggit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo
Source: https://github.com/maggit/claude-workspace/tree/main/skills/todo
Command: npx skills add https://github.com/maggit/claude-workspace --skill todo-maggit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a project, feature, or initiative into actionable tasks, producing a structured checklist with priorities, effort estimates, and dependencies that a team can immediately pick up and work from.

Core Features & Use Cases

Break down features into sprint-ready tasks with clear priorities and estimated effort.
Define dependencies and acceptance criteria to guide execution.
Plan across teams (product, design, engineering) and align with roadmaps.

Quick Start

Break down the project into a prioritized task list with dependencies and acceptance criteria.

Frequently Asked Questions about todo

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

FAQPage Schema

How do I break down a project into sprint-ready tasks with priorities and effort estimates?▼

To break down a project into sprint-ready tasks, provide a clear work description and optional constraints to generate a structured task list featuring priorities, effort estimates, dependencies, and acceptance criteria.

What is the best way to decompose a product feature into an actionable checklist for engineering and design teams?▼

Decomposing a product feature into an actionable checklist involves structuring tasks across engineering, design, and product roles, establishing dependencies and acceptance criteria to align execution with roadmaps.

Do I need to provide dependencies and acceptance criteria to generate a task list?▼

You must provide a clear work description to generate the task list, while constraints are optional; the output automatically defines dependencies and acceptance criteria to guide team execution.

Can I use this for agile planning across cross-functional teams like product and engineering?▼

Yes, agile planning with this approach supports cross-functional teams by breaking down initiatives into structured checklists that align product, design, and engineering execution with roadmap objectives.

What outputs should I expect when planning a roadmap and breaking down features?▼

When planning a roadmap and breaking down features, expect outputs including a defined objective, prioritized task list, effort estimates, dependencies, acceptance criteria, a dependency graph, and an effort summary.