plan-tasks

Break down project work into verifiable tasks with acceptance criteria and dependency ordering.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill plan-tasks-japurcell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-tasks
Source: https://github.com/japurcell/skills/tree/main/skills/plan-tasks
Command: npx skills add https://github.com/japurcell/skills --skill plan-tasks-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Tasks helps teams convert vague work items into small, verifiable tasks with explicit acceptance criteria and a defined dependency order, reducing ambiguity and rework.

Core Features & Use Cases

  • Task decomposition: break large work into manageable, testable tasks with clear criteria.
  • Dependency-aware planning: arrange tasks by dependency to minimize blockers.
  • Output generation: produce plan.md and todo.md to drive execution and tracking.

Quick Start

Invoke the plan-tasks skill to break down a feature spec into tasks and save the plan to plan.md and the task list to todo.md in the designated output path.

Frequently Asked Questions about plan-tasks

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

FAQPage Schema
How do I break down project work into verifiable tasks with acceptance criteria?

Task breakdown converts large feature specs into small, manageable items by defining explicit acceptance criteria for each task and arranging them by dependency order to minimize blockers and reduce rework.

What's the best way to organize a task dependency graph for a feature spec?

Organizing a task dependency graph involves reading feature specs, decomposing work into testable items, and arranging them sequentially based on dependencies to produce a structured plan and todo list for tracking.

How do I generate a plan.md and todo.md from a project specification?

Generating plan.md and todo.md from a specification involves analyzing specs in a read-only workflow, decomposing work into dependency-ordered tasks with acceptance criteria, and saving outputs to the designated .agents path.

Do I need subagents to plan tasks and define acceptance criteria?

You do not need standalone subagents to plan tasks, but the workflow coordinates with subagent-model-selection and planning components to read specs and output a structured task list for human review.

Can I use dependency-aware task breakdown for complex workflow planning?

Dependency-aware task breakdown supports complex workflow planning by arranging verifiable tasks according to their dependency graph, ensuring sequential execution and reducing blockers across the project lifecycle.