teamlead-core

Orchestrates a full-cycle development pipeline with agent routing, review, testing, and deployment stages.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill teamlead-core-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teamlead-core
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/teamlead-core
Command: npx skills add https://github.com/lfuuu/claude-rules --skill teamlead-core-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-agent software development work—routing tasks to the right specialists, enforcing review and testing gates, and managing commits, merges, and deploys—requires constant manual supervision. This Skill defines a stack-agnostic team-lead orchestrator that runs a fixed 12-stage pipeline autonomously, stopping only at defined human checkpoints. ## Core Features & Use Cases - Fixed 12-stage pipeline: Covers task intake, routing, planning, delegation, code review, documentation, testing, commit, merge, deploy, knowledge revision, and final reporting, with an explicit state-transition table for automatic stage advancement. - Human stop points: Pauses only for plan approval, merge to master, and production deploy; everything else proceeds autonomously without intermediate confirmation questions. - Delegation strategy: Chooses between spawning isolated subagents for large phases and inline skills for trivial work, with subagent nesting limited to one level. - Ralph loop mode: Supports an external restart loop where each iteration runs one phase in a fresh context window, using the todo file's phase table as cross-iteration memory. - Use Case: A project wrapper skill imports this core, fills in its routing table, delegate list, validation commands, and reviewer iteration limit, then runs a fullstack feature from an approved todo file through review, tests, and a single PR merge with only one human stop. ## Quick Start Import this skill from a project wrapper that defines the routing table, delegates, and validation commands, then ask the teamlead to run an approved todo file through the full pipeline.

Frequently Asked Questions about teamlead-core

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

FAQPage Schema
How do I orchestrate multi-agent development with a team-lead pipeline?

Define a project wrapper that imports this core skill and fills in the routing table, delegate list, validation commands, and reviewer iteration limit. The team-lead then runs tasks through stages 0-11 automatically, delegating implementation to specialist agents and stopping only at plan approval, merge, and production deploy.

When should I use subagents versus inline skills for delegation?

Spawn a subagent with an isolated context for large phases, big diffs, or work needing a clean session. Use an inline skill for trivial tasks, small diffs of one to three files, and short outputs like lint checks or non-production deploys.

What is the Ralph loop mode and when is it optimal?

Ralph mode restarts the team-lead as a fresh process per iteration, with each iteration completing exactly one phase and the todo file's phase table serving as memory. It is optimal when remaining phases would not fit in one context window, typically three or more independent, large, or cross-domain phases.

Can this skill be used directly without a project wrapper?

No. The skill is explicitly designed as an invariant core imported by reference from project wrappers. The wrapper must supply the routing table, delegates, validation and deploy commands, reviewer limits, and any degenerate stop points before the pipeline can run.

How does the pipeline handle review failures and test failures?

Reviewer CHANGES_REQUESTED routes work back to the same agent until the configured iteration limit, then escalates with options. Testing failures with a clear root cause route to the responsible zone's agent; unclear root causes trigger escalation with a diagnosis.

How do I detect a hung background Ralph iteration?

Check CPU growth by reading fields 14 and 15 of /proc/<pid>/stat twice with a 10-second interval. Growing CPU means the process is alive; unchanged file mtimes are not a reliable hang signal since review and testing stages legitimately avoid touching sources.