team-plan

Plans multi-task projects by decomposing work into scored tasks for agent team execution.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill team-plan-arangogutierrez
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: team-plan
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.claude/skills/team-plan
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill team-plan-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple AI agents on a multi-task project without a written plan leads to overlapping work, unclear task boundaries, and improvised branching. This Skill runs a structured planning phase on the agents-workbench branch that produces a scored, wave-organized plan before any agents are spawned. ## Core Features & Use Cases - Work decomposition with scoring: Breaks a project into independent tasks, scores complexity (1-4) and risk (likelihood x impact), and extracts shared infrastructure as a Task 0. - Wave planning and branch strategy: Groups more than 3 tasks into waves of at most 3, and requires an explicit branching strategy decision (per-task, shared feature branch, or single branch). - Plan artifact generation: Writes the plan to .agents/plans/<project-name>.md with a Task List, Risk Register, Dependencies Map, Path Ownership, and Success Criteria, then updates AGENTS.md. - Use Case: Before building rate limiting and audit logging into an API gateway, run the planning phase to get three approach options, scored tasks, a risk register, and a written plan that team-execute can pick up in a later session. ## Quick Start Ask the agent to run /team-plan with a project description such as "add rate limiting and audit logging to the API gateway" while on the agents-workbench branch.

Frequently Asked Questions about team-plan

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

FAQPage Schema
How do I plan a multi-agent project before spawning an agent team?โ–ผ

Run /team-plan with a project description while on the agents-workbench branch. It brainstorms at least three approaches, decomposes the work into scored tasks, asks for a branching strategy, and writes the plan to .agents/plans/ for team-execute to consume later.

How are tasks scored and organized into waves?โ–ผ

Each task gets a complexity score from 1 (trivial) to 4 (complex) and a risk score of likelihood times impact. Projects with more than 3 tasks are grouped into waves of at most 3, with dependencies placed in earlier waves and highest-risk tasks scheduled first.

When should I not use team planning for a task?โ–ผ

Skip it for single-file fixes or work one agent can finish solo. The pre-flight gate requires genuinely independent tasks and value that justifies the roughly 15x token cost of multi-agent coordination; otherwise use the solo subagent-driven-development path.

What happens if agents-workbench is behind the default branch?โ–ผ

The skill fetches origin and counts commits behind. Any positive count triggers a warning recommending a merge, and being more than 50 commits behind is a hard gate that refuses to plan until the branch is synced.

What branching strategies does the planning phase support?โ–ผ

Three options are offered as a mandatory question: one branch per task (recommended for independent work), a shared feature branch for tightly related features, or a single branch for small projects. The choice is recorded in the plan's Branch Strategy section.