Your first task

Follow one task from an issue link to a merged pull request. You make the decisions and write the code with your usual agent; PABLO handles everything in between.

Step by step#

1. Start the task#

   bash

   pablo task:start https://acme.atlassian.net/browse/PIM-123

   PABLO matches the link to one of your projects, creates the branch pim-123 and a worktree from the latest primary branch, and launches the task-analyst agent. It reads the ticket, its parent, linked pull requests and the relevant code, then writes a summary and an action plan. If the project has a startup script, it runs at the same time.

   No issue? Start from a sentence instead: pablo task:start --project wallet-kit "fix callback verification".

2. Check on it#

   bash

   pablo task:list

   The task shows up as 🔨 in-progress. The agents column shows 🏃 while the analyst works and 💭 when it's done and waiting for you. Prefer a browser? pablo web.

3. Read the plan, refine it#

   Open the analyst's session in Orca or OpenChamber. Read the plan, ask questions, push back. This is where you invest: the better the plan, the shorter the review later.

4. Write the code#

   Work in the task's worktree, with your own build agent or by hand. PABLO never writes code for you.

5. Open the pull request#

   In an OpenCode, Claude Code or Copilot session inside the worktree, run:

   /pablo-commit-and-pr

   It commits, pushes, opens the pull request as a draft with a written description, and hands the task back to PABLO in the draft state.

6. Let PABLO follow it#

   From now on the background poller checks the pull request every few minutes:

   • CI fails → 🔴 ci-red, and ci-analyst diagnoses the failure;
   • CI passes → the pull request leaves draft and the task waits for reviews;
   • a reviewer asks for changes → 🔁 request-changes, and pr-feedback turns the comments into a checklist;
   • approved → 🧪 needs-testing, waiting on QA;
   • QA flags a problem → 🚨 testing-failed, and task-feedback triages it.

   Each time you've fixed something, run /pablo-commit-and-pr again: the task goes back to draft and the loop continues.

7. Merge#

   Merge the pull request on GitHub as usual. PABLO notices, deletes the task and removes its worktree.

A real example#

What a task's life looks like, alternating between you and PABLO:

Where to go next#

• Managing tasks: everything you can do with a task (pause it, force a state, adopt an existing branch…).
• Task states: exactly what moves a task from one state to the next.
• Dashboard: the same picture in your browser.