Jobs
The task tracker that agents love using and humans love watching.
<img src="docs/static/screenshots/home.png" alt="Home dashboard" width="860"
Jobs is a CLI tool which helps agents create detailed plans and carry them out methodically.
A plan can contain blockers, acceptance criteria and hierarchy, making it a powerful hybrid of a spec/PRD and a directed acyclic graph (DAG). I like to say it “writes like a plan, runs like a DAG.”
Jobs is a replacement for Plan Mode, to-do tools, and task trackers. It comes with a rich dashboard because why not.
This document was written by a human for humans. If you're an agent, run job --help or check out the docs.
Workflow overview
- Have your agent read job schema and then write a Markdown document which starts with the “why” and ends with the “what:” a fenced YAML block with a hierarchical plan.
- Open the doc, review it, and edit as needed.
- Import the plan; start with job import plan.md --dry-run to check for errors, then drop the --dry-run.
- Have your agent run job status and claim the first task.
- Start the dashboard with job serve and observe.
While YAML is an objectively bad format, this particular YAML schema is quite readable for humans and easy for agents to generate, which put it ahead of Markdown or JSON.
Getting started
Install
$ go install github.com/bensyverson/jobs/cmd/job@latestThis drops the job binary into $HOME/go/bin (or $GOBIN if set). Make sure that directory is on your PATH.
AGENTS.md or CLAUDE.md
Add this line to your AGENTS file:
To create and manage plans and task lists, always use the `job` command.If you find the agent is still triggering its built-in Plan mode or to-do list tool, you can strengthen the language.