// skill

Co-op

Multi-phase plan protocol with color-coded teammate Claudes. Plans you don't lose track of after a coffee break — every step checked off with proof, every blocked step revisited later. The plan file is the source of truth, not your chat history.

// what it does

When you and Claude are working through a 20-step plan together, one of you forgets where you were after a coffee break. Co-op Mode keeps a shared journal in a markdown file. Every step is checked off with proof — a commit hash, a log line, a screenshot reference. Every blocked step gets a date stamp and a reason. Every session that resumes a plan reads the file and picks up exactly where the last one left off.

The novelty is the team mode. One Lead Claude session orchestrates; up to three teammate Claude sessions execute claimed rows in parallel. Each session has a color ID — G, B, Y, O — that matches the colors of your terminal windows so visual scan matches the plan file. Lead claims and assigns; teammates only execute their claimed rows. No two teammates ever touch the same file in the same step. Two unfinished rows touching the same path get sequenced, not parallelized.

The most underrated rule is the safe-reset checkpoint. Long sessions degrade in quality before you notice. Co-op detects clean phase boundaries (decision committed, plan up to date, no uncommitted code) and offers a copy-paste handoff prompt to start a fresh chat with zero context loss. The plan file carries the state — chat history is disposable.

// how to install

Download the file below — it's a single SKILL.md.
Save it to ~/.claude/skills/co-op/SKILL.md on your machine. Create the folder if it doesn't exist.
Restart Claude Code so the skill is picked up.
Start a plan: /co-op start plans/co-op/<your-plan-file>.md

trigger:/co-op

~ download SKILL.md →

// peek inside — the color vocabulary

| Color | Role     | Who                                            |
|-------|----------|------------------------------------------------|
| P     | Driver   | The user — always                              |
| G     | Lead     | Claude — orchestrator, assigns rows            |
| B     | Teammate | Claude — executes claimed rows only            |
| Y     | Teammate | Claude — executes claimed rows only            |
| O     | Teammate | Claude — executes claimed rows only            |

Rules:
- P never takes a Claude role. The user drives the Lead through prompts;
  G delegates to B/Y/O.
- Lead is fixed for the plan's lifetime. If the Lead session dies, a new
  G session resumes from the plan file.
- Teammates take orders only from Lead.
- One team per plan. Don't spawn overlapping teams across plans.