Tickets & PMO

The built-in PMO (Project Management Org) provides structured tickets, kanban boards, specs, and epics. Agents receive ticket context as structured prompts, not freeform chat.

Creating Tickets

$ prlt ticket create \
    --title "Implement rate limiting" \
    --description "Add rate limiting middleware to all /api routes" \
    --priority P1 \
    --category feature

Tickets support rich metadata:

Field	Description
`title`	Short summary of the work
`description`	Detailed description and context for the agent
`priority`	P0 (critical) through P3 (low)
`category`	feature, bug, refactor, test, docs, etc.
`labels`	Custom tags for filtering
`acceptance criteria`	Verifiable conditions for completion
`subtasks`	Breakdowns of the work

Acceptance Criteria

Acceptance criteria tell agents exactly what “done” looks like. Agents can check their work against these criteria before opening a PR.

$ prlt ticket create \
    --title "Add OAuth login" \
    --description "Support Google and GitHub OAuth providers" \
    --acceptance-criteria "OAuth redirect flow works" \
    --acceptance-criteria "Session persists after login" \
    --acceptance-criteria "Error handling for denied access"

Ticket Lifecycle

Tickets move through workflow columns on the kanban board:

Backlog — Created but not yet prioritized
Ready — Groomed and ready for an agent to pick up
In Progress — An agent is actively working on it
Review — Agent finished, PR open for review
Done — PR merged, work complete

# Move a ticket manually
$ prlt ticket move TKT-001 --column "Ready"

# Agents move tickets automatically during work execution

Specs

Specs are long-form documents that provide context across multiple tickets. Agents reference specs for consistent implementation.

$ prlt spec create \
    --title "Authentication System" \
    --file ./specs/auth-system.md

# Link a spec to tickets
$ prlt ticket update TKT-001 --spec "Authentication System"
$ prlt ticket update TKT-002 --spec "Authentication System"

Actions

Actions are reusable prompt templates that define how agents approach work:

Action	Description
`implement`	Build the feature or fix described in the ticket
`review`	Review code and provide feedback
`test`	Write tests for existing code
`refactor`	Improve code structure without changing behavior
`groom`	Break down a ticket into subtasks and acceptance criteria

# Spawn with a specific action
$ prlt work start TKT-001 --action implement
$ prlt work start TKT-001 --action review
$ prlt work start TKT-001 --action test

Tip

Create custom actions to match your team's workflow. For example, a “security-review” action that focuses on OWASP vulnerabilities.

External Issue Sources

Import tickets from external tools instead of creating them manually:

# Import from Linear
$ prlt work start --source linear:ENG-123

# Import from Jira
$ prlt work start --source jira:PROJ-456

# Import from Asana
$ prlt work start --source asana:1234567890

# Import from Shortcut
$ prlt work start --source shortcut:sc-789

See Integrations for setup instructions.

Getting Started

Core Concepts

Features

CLI Reference