team-plan
Team Plan
Write an implementation plan with team state tracking built in.
Announce at start: "I'm using the team-plan skill to create the implementation plan."
Process
Step 1: Delegate to obra writing-plans
REQUIRED SUB-SKILL: Use superpowers:writing-plans to generate the full plan.
Follow writing-plans exactly. Save plan to docs/plans/YYYY-MM-DD-<feature-name>.md.
Step 2: Add resume header
At the top of the generated plan (after the main header), add:
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-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.
9team-execute
Use when you have a plan created by team-plan. Orchestrates Developer and Architect agents per task with progress tracking and state persistence for resumability.
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