team-init

Install a Claude Code agent team into ~/.claude/agents/ from an interview.

123|22|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/AlexZio00/claude-code-skills --skill team-init-alexzio00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-init
Source: https://github.com/AlexZio00/claude-code-skills/tree/main/team-init
Command: npx skills add https://github.com/AlexZio00/claude-code-skills --skill team-init-alexzio00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Permanently installs a Claude Code agent team — orchestrator, reviewers, implementers — into ~/.claude/agents/ from a short interview. It codifies a safe, repeatable setup flow that wires the harness prerequisites and preserves existing custom agents.

Core Features & Use Cases

  • Interview-driven team assembly that creates individualized agent files (orchestrator, code-reviewer, verification, brainstorming, writing-plans) and places them in ~/.claude/agents/.
  • Orchestrator-enabled governance with drift detection and gate enforcement to prevent premature finish declarations.
  • Non-destructive, merge-safe behavior: existing agents are preserved; orchestrator prompts for update/replace when needed; supports future scaling.

Quick Start

Run /project-init, then /harness-init, then /team-init to install the full Claude Code agent team.

Frequently Asked Questions about team-init

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

FAQPage Schema
How do I set up a Claude Code agent team for local project automation?

Installing a Claude Code agent team is automated through an interview-driven flow that provisions orchestrator, reviewer, and implementer agents into your local environment for project governance and task execution.

Can I generate Claude Code orchestrator and reviewer agents without overwriting my existing files?

Yes, agent generation uses non-destructive, merge-safe behavior that preserves existing custom agents. The orchestrator prompts for update or replace permissions when conflicts occur, ensuring your current setup remains intact.

What is the process for wiring Claude Code harness prerequisites during initial project setup?

Harness prerequisites are wired through a prerequisites-driven interview flow that assesses project needs and generates phase-based agents, establishing governance with drift detection and gate enforcement to prevent premature finish declarations.

Do I need to run specific commands before installing agent teams with team-init?

Yes, you must run /project-init and /harness-init before executing /team-init to ensure the environment is fully prepared for the permanent installation of the Claude Code agent team.

What types of agents are permanently installed into the ~/.claude/agents/ directory?

The installation provisions individualized agent files including an orchestrator, code-reviewer, verification, brainstorming, and writing-plans agents, all permanently placed in the ~/.claude/agents/ directory.

Why does the Claude Code orchestrator enforce gates and drift detection during task execution?

The orchestrator enforces gates and drift detection to prevent premature finish declarations, ensuring that implementers complete all task requirements accurately before a project phase is considered complete.