team-execute
Team Execute
Orchestrate implementation of a plan using named Developer and Architect agents.
Announce at start: "I'm using the team-execute skill to implement this plan."
Setup
Step 1: Locate plan and state
Ask user for plan path if not provided. State file is <plan-path-without-extension>.state.json.
Read both files. If state file doesn't exist, assume all tasks pending.
Step 2: Set up worktree
REQUIRED SUB-SKILL: Use superpowers:using-git-worktrees to create or switch to the feature worktree.
Save worktree path and branch to .state.json.
More from wjaszczuk/agent-team-skills
team-brainstorming
Use when starting any new feature or task. Wraps obra brainstorming but replaces the final writing-plans step with team-plan, so the generated plan includes state tracking and is ready for team-execute.
10team-plan
Use when you have a spec or requirements for a multi-step task. Extends obra writing-plans with team state tracking and resumability support.
9team-architect
Architect/CR agent role. Receives git diff, task spec, ADRs, design doc, and project conventions. Reviews code and returns APPROVED or CHANGES_REQUIRED. Do NOT invoke directly — dispatched by team-execute.
9team-developer
Developer+Tester agent role. Receives task text, context, worktree path, and branch. Implements using TDD, commits, and pushes. Do NOT invoke directly — dispatched by team-execute.
9agent-team-skills
Team-based implementation skills. Use team-plan to write plans with state tracking, team-execute to run them with named Developer and Architect agents.
1