plan-to-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.

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.

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.

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.

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.

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.