plan-to-tasks

Convert user plans into structured tasks for docs/IMPLEMENTATION.md.

60|8|Updated Feb 15, 2026

Search Tags:#automation #dependency-graph #task-generation #phase-management #plan-to-tasks #implementation-docs

Ready to run

npx skills add https://github.com/albinotonnina/echos --skill plan-to-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-to-tasks
Source: https://github.com/albinotonnina/echos/tree/main/.claude/skills/plan-to-tasks
Command: npx skills add https://github.com/albinotonnina/echos --skill plan-to-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates scattered plans (in memory, in a file, or described inline) into a precise, executable set of tasks that populate docs/IMPLEMENTATION.md in the standard format, enabling automated task execution workflows.

Core Features & Use Cases

Converts plan content into agent-executable tasks following the project's IMPLEMENTATION.md template.
Reads and aligns with existing phase numbering to maintain a coherent dependency graph.
Generates clear acceptance criteria, dependencies, and task boundaries to enable independent execution.
Supports both single-step plans and multi-phase plans, adapting to varying levels of detail.

Quick Start

Provide a plan description in any supported format and ask the AI to convert it into a complete IMPLEMENTATION.md task set.

Frequently Asked Questions about plan-to-tasks

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

FAQPage Schema

How do I convert a project plan into agent-executable tasks?▼

To convert a project plan into agent-executable tasks, provide your plan description from memory, a file, or inline text. The tool translates it into a phase-based task plan with clear dependencies, acceptance criteria, and task boundaries formatted for docs/IMPLEMENTATION.md.

What is the best way to structure implementation docs for automated task execution?▼

The best way to structure implementation docs for automated task execution is using a phase-based format with clear dependencies and acceptance criteria. This approach reads and aligns with existing phase numbering to maintain a coherent dependency graph for agent workflows.

Can I generate a multi-phase task plan from an inline description?▼

Yes, you can generate a multi-phase task plan from an inline description. The tool supports both single-step plans and multi-phase plans, adapting to the varying levels of detail provided in your input to populate the IMPLEMENTATION.md file.

How does phase management work when adding new tasks to an existing IMPLEMENTATION.md file?▼

Phase management works by reading and aligning with existing phase numbering in your IMPLEMENTATION.md file. This ensures new tasks maintain a coherent dependency graph and follow exact template rules for build and test prerequisites.

Do I need a dependency graph to structure my project tasks?▼

A dependency graph is essential to structure project tasks for independent execution. The tool generates clear task boundaries and dependencies, ensuring each phase and task is numbered correctly and validated against build and test prerequisites.

Why are acceptance criteria important for task generation in implementation docs?▼

Acceptance criteria are important for task generation because they enable independent agent execution. The tool enforces exact template rules and generates clear acceptance criteria, dependencies, and task boundaries within your IMPLEMENTATION.md file.