Coordinates peer Claude Code sessions across managed projects via claude-hive messaging.
npx skills add https://github.com/fryanpan/ai-team-lead --skill team-lead-fryanpan
Please help me install this Agent Skill. Skill: team-lead Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/team-lead Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill team-lead-fryanpan
list_peers, send_message, set_summary) to find active sessions and delegate work via stable_ids that survive restarts. - Goal-level delegation: Delegates in problem space (goals, deadlines, success criteria) rather than solution space, letting each peer apply its own local context. - Cross-project tracking and escalation: Maintains a written plan, tracks goals and blockers across peers, and surfaces human-only steps and decisions to the user. - Use Case: You run six side projects, each with its own Claude Code session. The team-lead session checks each peer's summary, delegates the week's goals, notices one peer is blocked on an OAuth flow only you can complete, and nudges you at the right moment. ## Quick Start Ask the team lead to list active peers and delegate this week's goals from the plan to each project session.High-intent search queries and answers about installing and using this skill.
Run one session as a team lead connected to peers through the claude-hive MCP broker. Use list_peers to discover active sessions, then delegate goals with send_message, referencing peers by their stable_id so messaging survives session restarts.
Delegate in problem space: state the goal, deadline, and success criteria rather than specific files or commands. The receiving session has local context you lack, so over-specifying tactics overrides its knowledge and can silently bypass work already in progress.
A session_id rotates on every restart and breaks message continuity, while a stable_id is derived from sha256 of the git root or working directory and persists across restarts. Always delegate using stable_ids so messages reach the right workspace mailbox.
No. The team lead never edits other project repos directly; it proposes changes through GitHub PRs and delegates implementation to that project's peer session. Before reading from a project it runs git pull --ff-only to ensure freshness.
Almost always. A peer refusing a delegation with concrete concerns usually has session-local context about user criteria, repo conventions, or prior decisions. The team lead should listen, flag the conflict to the user, and avoid re-explaining or overriding.
AradotsoDiscover and message Claude Code instances via a local MCP broker.
AppsVortexCoordinate batch PR merges across GitHub or Bitbucket with conflict handling.
tlennon-ieCoordinate cross-repo backporting with one PR per sibling repository.
EvoClawDispatch parallel subagents to run independent experiments concurrently.