proletariat
Documentation Menu

Getting Started

Core Concepts

Features

CLI Reference

Work Execution

Work execution is the core loop: assign a ticket to an agent, the agent runs autonomously, and delivers a PR when done. Proletariat handles branching, session management, and status transitions automatically.

Starting Work

The simplest way to start work is with prlt work start. Proletariat assigns an agent, creates a branch, opens a tmux session, and injects the ticket as a structured prompt.

# Start work on a single ticket
$ prlt work start TKT-001

# Start with a specific agent
$ prlt work start TKT-001 --agent bezos

# Start with a specific action
$ prlt work start TKT-001 --action implement

Batch Spawning

Spawn multiple agents at once to parallelize work across your backlog:

# Spawn all tickets in a column
$ prlt work spawn --column "Ready" --all

# Spawn the top 5 by priority
$ prlt work spawn --count 5

# Multi-select which tickets to spawn
$ prlt work spawn --many

# Spawn specific tickets
$ prlt work spawn TKT-001 TKT-002 TKT-003

# Preview what would happen without spawning
$ prlt work spawn --dry-run

Tip

Use --dry-run to preview which agents would be assigned and what branches would be created before committing.

Diet-Balanced Spawning

Diet ratios ensure your team works on a balanced mix of categories (features, bugs, support, etc.) rather than just picking whatever is at the top of the backlog.

# View current diet ratios
$ prlt diet

# Set diet ratios
$ prlt diet --set "ship=4,grow=2,support=1"

# Spawn using diet-balanced selection
$ prlt work spawn --diet --count 10

# Pull tickets to Ready column using diet ratios
$ prlt pull --count 20

What Happens During Execution

  1. Branch creation — A conventional branch is created (e.g., TKT-001/feat/agent-name/repo/title-slug)
  2. Session launch — A tmux session starts with the AI coding tool
  3. Prompt injection — The ticket (title, description, AC, subtasks, specs) is injected as a structured prompt
  4. Autonomous work — The agent codes, commits, and tests
  5. Completion — The agent signals done, a PR is opened, and the ticket moves to Review

Monitoring Work

# Check status of all active work
$ prlt work status

# Peek at an agent's output (non-interactive)
$ prlt session peek bezos

# Send a message to a running agent
$ prlt session poke bezos "Focus on the unit tests first"

# Attach to an agent's tmux session
$ prlt session attach bezos

Completing Work

When an agent finishes, it marks its work as ready for review:

# Agent marks its own work ready (creates PR)
$ prlt work ready TKT-001 --pr

# Or mark ready without a PR
$ prlt work ready TKT-001 --no-pr

# Mark work as fully complete (post-review)
$ prlt work complete TKT-001

Review Pipeline

Proletariat includes a review pipeline that can automate code review with agents:

# Start a review cycle
$ prlt work review TKT-001

# The pipeline: review → fix → re-review until approved

Note

The review pipeline runs a reviewer agent that reads the PR diff and provides feedback. If changes are needed, the original agent is re-spawned to address them.

External Issue Sources

Start work directly from external tools without manually creating tickets:

# From Linear
$ prlt work linear ENG-123

# From Jira
$ prlt work jira PROJ-456

See Integrations for setup and supported sources.