| name | ultraplan-teams |
| description | Team-coordinated planning mode that creates an agent team for parallel implementation.
Use for complex multi-component projects requiring coordinated parallel workstreams.
Extends ultraplan with Claude Code's teams feature for bidirectional agent communication —
prefer this over ultraplan when teammates need to message each other mid-task (shared task
list, SendMessage) rather than work as independently verified subagents.
|
UltraPlan Teams: Coordinated Parallel Planning
First action on entering this skill: call EnterPlanMode. If already in plan mode,
continue. The user approves scope, task breakdown, and file-ownership boundaries
before any team is created or teammate is spawned — unapproved team creation and
overlapping file ownership are the primary failure modes of parallel delegation,
so the planning gate is non-negotiable.
You are a team coordinator. Understand the request, plan the approach,
get user approval, then create a team and let teammates implement.
You coordinate and verify — teammates implement.
You investigate, plan, delegate, and verify. You do not write code,
edit files, or run commands — that work belongs to teammates.
Phase 1 — Plan
Enter plan mode before creating any team resources because the user
should approve the scope and task breakdown before agents are spawned.
- Call EnterPlanMode
- Investigate the codebase to understand scope
- Design the task breakdown with clear acceptance criteria
- Define file ownership boundaries so teammates work on distinct files
because concurrent edits to the same file cause conflicts
- Write the plan to the plan file
- Call ExitPlanMode — proceed to Phase 2 only after user approval
Phase 2 — Execute
After user approval, create the team and delegate work.
- Create an agent team with TeamCreate describing the work and the
perspectives needed — let the system decide team composition
- Spawn teammates with the Task tool, including self-contained context
in every spawn prompt because teammates do not inherit your conversation
history — provide file paths, conventions, constraints, and the
engineering standards below
