team-lead

Name: team-lead
Availability: InStock
Author: 0xobat

Orchestrate parallel feature development across agents using isolated git worktrees.

Updated Feb 22, 2026

Search Tags:#devops #git workflow #agent orchestration #agile #parallel development #feature implementation

Ready to run

npx skills add https://github.com/0xobat/claude-skills --skill team-lead-0xobat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-lead
Source: https://github.com/0xobat/claude-skills/tree/main/dev/skills/team-lead
Command: npx skills add https://github.com/0xobat/claude-skills --skill team-lead-0xobat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the development process by enabling multiple agents to work on independent features concurrently, significantly reducing project timelines.

Core Features & Use Cases

Parallel Development: Orchestrates multiple agents using isolated git worktrees to implement features simultaneously.
Wave-Based Execution: Organizes features into dependency-ordered waves for safe parallel execution.
Conflict Resolution: Manages merge conflicts and ensures the main branch remains stable.
Use Case: When a project has 5 independent features ready for implementation, use this Skill to assign each feature to a separate agent working in its own worktree, drastically cutting down the time to completion compared to sequential development.

Quick Start

Use the team-lead skill to orchestrate parallel feature development for three or more independent features.

Frequently Asked Questions about team-lead

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

FAQPage Schema

How do I implement multiple independent features in parallel using git worktrees?▼

Parallel feature implementation uses isolated git worktrees to dispatch multiple agents concurrently. It organizes features into dependency-ordered waves, allowing simultaneous development while maintaining main branch stability through merge verification.

What is the best way to orchestrate multiple agents for concurrent software development?▼

Agent orchestration for concurrent software development is managed by dispatching agents across isolated git worktrees. This approach handles wave-based execution and conflict resolution, ensuring independent features are implemented simultaneously without branch instability.

How do I manage git merge conflicts when agents work on parallel features?▼

Merge conflicts during parallel feature development are managed through automated verification and conflict resolution. The system validates baselines before merging, ensuring that concurrent feature waves integrate smoothly without compromising the main branch.

Do I need specific configuration files to run parallel feature waves with isolated worktrees?▼

Yes, running parallel feature waves requires a `features.json` file for tracking feature status and a `verify.sh` script. These components provide the necessary baseline validation and post-merge verification for harness-based projects.

Can I use parallel development workflows for features with dependencies?▼

Yes, parallel development workflows support features with dependencies through wave-based execution. Features are organized into dependency-ordered waves, ensuring that prerequisite features are fully implemented and merged before dependent features begin.

Why does parallel agent orchestration require isolated git worktrees?▼

Isolated git worktrees are required for parallel agent orchestration to provide each agent with a clean, independent working directory. This isolation prevents file conflicts during simultaneous feature implementation and safeguards main branch stability until successful merge verification.