Dev workflow

Most of the time Leroy works tickets on its own. But sometimes you want to pick one up yourself — to pair on it, take over a tricky change, or start fresh from your editor. The MCP gives you the same context Leroy uses, so you cold-start without digging through tabs. Here's the loop.

01 Find the work

Start with a question. leroy_ask_leroy answers in plain English and hands back the ticket ids it referenced, so you can ask broadly and drill in:

Use leroy: what's open against payments-api right now, and which ones are blocked on me?

If you already know the shape of what you want, skip the synthesis and filter directly with leroy_find_tickets (by status, keyword, or ref) or cast a wider net with leroy_search across titles, bodies, and conversations. Either way you end up with a ticket ref to work.

02 Pull context to start

Before you write a line, pull the context pack with leroy_get_ticket_context. It returns the ticket body, related code references, prior decisions, and a suggested base branch — enough to cold-start the change without spelunking:

Use leroy to pull the full context for PIT-412 and set me up to start it locally.

Need the whole picture — every comment, the full plan, the linked PR? Reach for leroy_get_ticket (or pass response_format: DETAILED). And if Leroy has already drafted an execution plan, leroy_get_planshows the per-repo branches, what's done vs. left, and any open questions you can pick up from.

03 Do the work

Now you're in your normal loop — edit, run, commit — with the context already loaded into your tool. If a ticket is mid-flight with an agent run, leroy_get_execution tells you the current stage, what's blocking, the branch and PR, and the cost so far, so you don't step on work that's already moving.

04 Check PRs & attention

When you push, the change shows up alongside everything else Leroy is shipping. Use leroy_list_pull_requests to see the PRs open across the account, and leroy_my_attentionto see what's actually owed by you — reviews, plan approvals, clarifications — without switching to the web app:

Use leroy to show what's waiting on me and list the open PRs.

That closes the loop: you found the ticket, pulled its context, did the work, and checked what's left — all from the editor.