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>orlinear/<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