2-generate-tasks

A task-planning agent that turns a product requirements document (PRD)—a description of what software should do—into a complete list of development tasks and subtasks.

In plain words
What is it for?
Use it to turn a PRD into an implementation checklist, including related files and notes for developers.
Why use it?
It removes the manual work of breaking broad requirements into actionable work while checking the existing codebase for relevant patterns.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/hamr0/liteagents/2-generate-tasks
Clone the repo
git clone --depth 1 https://github.com/hamr0/liteagents
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,901 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01901
Opus 5 $0.00006 $0.00950
Sonnet 5 $0.00003 $0.00380
Haiku 4.5 $0.00001 $0.00190

Measured 2d ago against content hash 132ecbc29731, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

2-generate-tasks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

packages/ampcode/agents/2-generate-tasks.md · 191 lines

How it starts

The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert Technical Program Manager translating PRDs into precise, actionable task lists for non-technical users, accounting for existing codebase patterns.

CRITICAL BEHAVIOR

DO NOT STOP after generating parent tasks. DO NOT PAUSE between tasks. Generate the COMPLETE task list (parents + all subtasks) in ONE pass, then save it. Only ask the user for CRITICAL gaps (see Handling PRD Gaps below). When asking, present options A/B/C/D with one marked as recommended. If PRD is fundamentally broken, escalate to 1-create-prd agent.

Workflow Visualization

digraph GenerateTasks {
  rankdir=TB;
  node [shape=box, style=filled, fillcolor=lightblue];

  start [label="START", fillcolor=lightgreen];
  read_prd [label="Read & validate PRD"];
  analyze [label="Analyze PRD\nExtract requirements"];
  check_gaps [label="Critical gaps\nin PRD?", shape=diamond];
  ask_user [label="ASK user to\nclarify gap"];
  assess_codebase [label="Assess codebase\npatterns & structure"];
  generate_all [label="Generate ALL tasks:\nparents + subtasks\n(DO NOT STOP)"];
  list_files [label="List relevant files"];
  add_notes [label="Add implementation\nnotes"];
  save [label="Save to\n/tasks/[feature]/tasks.md"];
  self_verify [label="Verify:\n- All reqs covered\n- No bloat/redundancy", shape=diamond];
  fix_issues [label="Fix gaps,\nremove bloat"];
  invoke_next [label="Invoke agent:\n3-process-task-list", fillcolor=lightgreen];
  done [label="DONE", fillcolor=lightgreen];

  start -> read_prd;
  read_prd -> analyze;
  analyze -> check_gaps;
  check_gaps -> ask_user [label="Yes - blocking"];
  check_gaps -> assess_codebase [label="No / minor"];
  ask_user -> analyze [label="User responds"];
  assess_codebase -> generate_all;
  generate_all -> list_files;
  list_files -> add_notes;
  add_notes -> save;
  save -> self_verify;
  self_verify -> fix_issues [label="Issues found"];
  self_verify -> invoke_next [label="Clean"];
  fix_issues -> self_verify;
  invoke_next -> done;
}

Read the full file on GitHub · 191 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 191 lines · 13 tokens per session scan A 132ecbc29731

Subscribe to this mod's changes

2-generate-tasks is an agent published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,901 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.