How do I install the Plan To Tasks skill?

Run npx skillmds@latest add tomevault-io/plan-to-tasks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan To Tasks safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan To Tasks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan To Tasks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan To Tasks?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan To Tasks by tomevault-io — Agent Skill

Name: Plan To Tasks
Author: tomevault-io

Plan To Tasks

Convert a software feature plan into a structured JSON task list. Use when the user wants to transform a project plan or PRD into implementable tasks, break down a feature into actionable steps, or generate a prd.json file from a plan document. Triggers include "convert plan to tasks", "create tasks from plan", "generate task list", "break down this plan", or providing a path to a plan file in .agent/projects/. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Plan to Tasks

Convert software feature plans into structured JSON task lists for agent implementation.

Workflow

Read the plan file at .agent/projects/<PROJECT_NAME>/<PLAN_FILE>.md
Analyze the plan and break into implementable tasks
Identify any prerequisites requiring human action
Write task list to .agent/projects/<PROJECT_NAME>/prd.json
Write prerequisites (if any) to .agent/projects/<PROJECT_NAME>/prerequisites.md

Task Format

See references/task-creation-guidelines.md for the complete JSON schema.

Each task includes:

id: <FEATURENAME>-<INCREMENTING_ID>
branchName: <NOTICKET-featureName> or linear/<TICKETNAME>
title: Brief task description
implementationSteps: Array of steps to implement
acceptanceCriteria: Array of verification checks
passes: Boolean (default false)

Guidelines

Tasks should be completable via code and terminal commands - writing/editing files (JS, k8s YAML, Dockerfiles) and running commands.

Frontend code requires UI validation tasks - when React, Svelte, etc. are involved, include tasks for verifying work in the browser. Space these roughly every 5 tasks throughout the list.

Include unit tests - add vitest tests for functions and components that would benefit from testing.

Human prerequisites go in prerequisites.md - actions requiring human intervention (provisioning API tokens, setting up external infrastructure, creating VMs/k8s clusters) should not be tasks. Document these in .agent/projects/<PROJECT_NAME>/prerequisites.md as instructions for humans to complete first.

Resources

references/

task-creation-guidelines.md - JSON schema and examples for task format

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: plan-to-tasksdescription: Convert a software feature plan into a structured JSON task list. Use when the user wants to transform a project plan or PRD into implementable tasks, break down a feature into actionable steps, or generate a prd.json file from a plan document. Triggers include "convert plan to tasks", "create tasks from plan", "generate task list", "break down this plan", or providing a path to a plan file in .agent/projects/. Use when this capability is needed.---# Plan to TasksConvert software feature plans into structured JSON task lists for agent implementation.## Workflow1. Read the plan file at `.agent/projects/<PROJECT_NAME>/<PLAN_FILE>.md`2. Analyze the plan and break into implementable tasks3. Identify any prerequisites requiring human action4. Write task list to `.agent/projects/<PROJECT_NAME>/prd.json`5. Write prerequisites (if any) to `.agent/projects/<PROJECT_NAME>/prerequisites.md`## Task FormatSee [references/task-creation-guidelines.md](references/task-creation-guidelines.md) for the complete JSON schema.Each task includes:- `id`: `<FEATURENAME>-<INCREMENTING_ID>`- `branchName`: `<NOTICKET-featureName>` or `linear/<TICKETNAME>`- `title`: Brief task description- `implementationSteps`: Array of steps to implement- `acceptanceCriteria`: Array of verification checks- `passes`: Boolean (default false)## Guidelines**Tasks should be completable via code and terminal commands** - writing/editing files (JS, k8s YAML, Dockerfiles) and running commands.**Frontend code requires UI validation tasks** - when React, Svelte, etc. are involved, include tasks for verifying work in the browser. Space these roughly every 5 tasks throughout the list.**Include unit tests** - add vitest tests for functions and components that would benefit from testing.**Human prerequisites go in prerequisites.md** - actions requiring human intervention (provisioning API tokens, setting up external infrastructure, creating VMs/k8s clusters) should not be tasks. Document these in `.agent/projects/<PROJECT_NAME>/prerequisites.md` as instructions for humans to complete first.## Resources### references/- `task-creation-guidelines.md` - JSON schema and examples for task format---> Converted and distributed by [TomeVault](https://tomevault.io/claim/daftgopher) — claim your Tome and manage your conversions.

Frequently asked questions