tl

Manage a Relay program as a tech lead coordinating worker agents and pull requests.

3|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ronaknnathani/relay --skill tl-ronaknnathani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tl
Source: https://github.com/ronaknnathani/relay/tree/main/skills/tl
Command: npx skills add https://github.com/ronaknnathani/relay --skill tl-ronaknnathani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a multi-pull-request engineering program across many worker agents is hard to keep consistent: goals drift, decisions get lost in conversation, capacity limits are violated, and merged work leaves stale sessions and branches behind. This Skill turns the agent into a single CEO-facing tech lead that keeps all program truth durable on disk and drives work through the Relay CLI. ## Core Features & Use Cases - Program governance: Shape goals in goal.md, publish immutable versioned architecture contracts, and record every open question or conflict as a durable program decision surfaced to the CEO. - Dependency-aware dispatch: Decompose work into PR-sized items with priorities, dependencies, and pinned contracts, then dispatch each through deliver-pr with a dedicated Herdr worker tab. - Capacity and lifecycle management: Serialize open-PR grants with grant-open-pr/can-open-pr, route CEO change requests via worker request-change, and retire merged items with worker cleanup. - Use Case: A CEO asks to migrate an authentication system across three repositories. The tech lead shapes the goal, publishes contracts, decomposes the work into ordered items, dispatches senior worker agents, and reports status while never writing production code or merging pull requests. ## Quick Start Ask the agent to resume and manage the Relay program for a given slug, for example: run the tl skill with my-program to check patrol status, process worker mail, and dispatch the next ready item.

Frequently Asked Questions about tl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a multi-pull-request program with coding agents?▼

Use the Relay program model: a tech lead agent shapes the goal, publishes versioned architecture contracts, decomposes work into dependency-ordered items, and dispatches each item through deliver-pr to a dedicated worker session. All state stays durable on disk under ~/.relay.

How does the tech lead skill coordinate worker agents?▼

Workers run as senior engineers in their own Herdr tabs, owning clarify, plan, implementation, and pull requests. The tech lead coordinates through durable mailboxes, program decisions, and contracts, never through direct worker-to-worker prompts.

Does the Relay tech lead skill require Herdr?▼

Yes. Managed programs run only under Herdr; every managed command verifies the herdr binary, the owning pane, and a reachable Herdr server before acting. There is no plain-terminal fallback, and readiness errors must be reported rather than worked around.

How are CEO change requests on open pull requests handled?▼

Route them with relay program worker request-change, which reads the pull request's current GitHub state first. Open unapproved PRs go back to the same worker, approved or queued PRs become pending follow-up items, and merged PRs spawn a new dispatched item.

What are the limitations of the tech lead skill?▼

The tech lead never writes production code, approves or merges pull requests, or invokes stack-ship inside a program. At most three linked child pull requests may be open at once, and scheduled standing QA is not implemented in V1.