Issue-to-run workflow
Readiness checks, human clarification, task envelopes and isolated worktrees connect GitHub requirements to agent work.
Developer Agent Collaboration
Developer tooling that turns GitHub work into coordinated coding-agent runs with local peer messaging, explicit ownership and reviewable handoffs.
My role
Implemented issue-workflow extensions, orchestration logic and a local peer-coordination package on top of third-party Pi.
The problem
Parallel coding agents can duplicate work, collide on files and lose the connection between an issue, its acceptance criteria and the evidence needed to finish it.
The approach
Built a family of Pi extensions and packages for preparing issues, creating isolated workspaces, orchestrating scout–plan–writer–review phases and coordinating peer sessions through local messaging and persistent goal/run records.
What it enables
Enables more inspectable delegation and multi-agent work, with clearer next actions, bounded collaboration loops and separate review evidence. The tools extend an existing coding-agent runtime rather than replace or claim authorship of it.
The work,
and its boundaries.
Complementary agent roles
Scout and planning stages precede one writer and independent review; read-only research fanout can be combined before implementation.
Peer coordination
Repository-scoped messaging, persistent goals, claims, heartbeats and bounded supervisors help agents share findings and avoid duplicate work.
Architecture and scope
Pi hosts the extensions; GitHub/worktree adapters manage issue work, local transport connects peers, and ledgers retain run evidence. Peer factory commands primarily record and recommend checks and PR actions; they do not automatically prove or ship changes.
Technology
- TypeScript
- JavaScript
- Node.js
- GitHub CLI
- Git worktrees
- Pi extension API
- Local sockets
- JSONL
Let’s make your next project workable.
Talk with me about the product, the engineering and the decisions that need to stay with people.