hanh9898

Matt With Paseo — Development skill for Claude Code

Development community

A simple multi-agent orchestrator: Matt Pocock's skills + the Paseo agent control plane, running tickets in waves of parallel agents, and many ticket sets as streams that each ship through one pull re.

How to install Matt With Paseo

This entry records only its repository, not the path inside it, so there is no exact command to give. Open hanh9898/matt-with-paseo and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Matt With Paseo does

A simple multi-agent orchestrator: Matt Pocock's skills + the Paseo agent control plane, running tickets in waves of parallel agents, and many ticket sets as streams that each ship through one pull request or GitLab merge request.

Alternatives in Development

  • Zeron — A native control plane for Claude Code, Codex, Cursor, Devin and other coding agents 1.4k ★
  • OpenSquirrel — For people who get distracted by agents 1.3k ★
  • Agentcontrolplane — ACP is the Agent Control Plane - a distributed agent scheduler optimized for simplicity, clarity, and control 463 ★

README

matt-with-paseo

A simple multi-agent orchestrator for Claude Code. It combines [Matt Pocock's skills](https://github.com/mattpocock/skills) (grill, spec, tickets, TDD, code review) with [Paseo](https://paseo.sh), a control plane for running many coding agents at once.

You write the tickets with Matt's skills. `matt-with-paseo` runs them in **waves**: every ticket gets its own Paseo agent in its own git worktree, and the orchestrator merges, reviews, and cleans up before starting the next wave. When several ticket sets must run and ship on their own at once, a second skill, `matt-with-paseo-streams`, runs each set as a **stream** from one control folder (see [Streams](#streams-many-ticket-sets-at-once)).

Why

Matt Pocock's skills take a feature from a vague idea to a set of small, dependency-ordered tickets. Running those tickets is still sequential by default: `/mattpocock-skills:implement` works through them one at a time in a single session.

Paseo can run many agents in parallel, each in its own worktree. What it does not know is which tickets are safe to run together, what each agent needs to be told, or how to check and merge the results.

`matt-with-paseo` fills that gap with the wave skill:

  • It locates where your work stands (not configured, no spec yet, spec, tickets, a wave in progress, finished) and suggests one next step.
  • It names a wayfinder map as a set of decision tickets not yet through /mattpocock-skills:to-spec, and starts no wave on it.
  • It splits tickets into waves from their Blocked by lines, so only independent tickets run side by side.
  • It writes one common rules file per wave, so every agent gets the same context and each prompt stays four lines long.
  • It checks each agent's work against the real artifacts (commits, ticket status, a re-run of the key claim) instead of trusting the report.
  • It merges each ticket as soon as it checks out, starts the tickets that merge unblocks, reviews the *seams