@eddiedao/team-auto 1.0.0 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eddiedao/team-auto",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Claude Code skill: Auto-orchestrate Agent Teams from GitHub issues with planning, implementation, review, and merge workflows.",
   "keywords": ["claude-code", "claude-skill", "agent-teams", "github-issues", "ai-orchestration"],
   "author": "eddy",

package/skill/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-auto
 description: "Auto-orchestrate Agent Teams from GitHub issues. Spawns lead + dev/reviewer/designer agents in worktrees, plans with opus, implements with sonnet, reviews before merge."
-version: 1.0.0
+version: 1.1.0
 argument-hint: "[--devs N] [--reviewers N] [--designers N] [--branch <base>]"
 ---
 
@@ -40,19 +40,45 @@ Lead decides roles based on issues (minimum team = 1 developer + 1 reviewer):
 
 Lead model: `claude-opus-4-5-20251101`. Lead NEVER touches code — coordination only.
 
-## Step 3: Spawn Teammates
+## Step 3: Create Worktrees + Spawn Teammates
 
-For each teammate, spawn with `isolation: "worktree"` and `display: "split"`:
+**3a. Create git worktrees** (lead runs these BEFORE spawning):
+
+For each developer/designer teammate, use the `/ck:worktree` skill's script:
+```bash
+node $HOME/.claude/skills/worktree/scripts/worktree.cjs create "<issue-slug>" --prefix feat --json
+```
+
+Parse the JSON output to get the `worktreePath` and `branch` for each teammate.
+
+Reviewers do NOT need worktrees (read-only work).
+
+**3b. Spawn teammates** with `mode: "plan"` and `display: "split"`:
 - `model: "claude-opus-4-5-20251101"` (planning phase)
 - Include CK Context Block (see below) + role-specific skills in prompt
 - Each agent gets assigned issue(s)
+- **CRITICAL:** `mode: "plan"` forces teammate into plan-only mode — no file edits until plan is approved
+- **CRITICAL:** Include worktree path from 3a output in spawn prompt: `"Your working directory is: <worktreePath>. Run all commands from this directory."`
+
+**NOTE:** `isolation: "worktree"` is a subagent-only feature. Agent Teams teammates need worktree setup via `/ck:worktree` script.
+
+## Step 4: Teammate Workflow (INLINE in spawn prompt)
 
-## Step 4: Teammate Workflow (in spawn prompt)
+Lead MUST read `references/teammate-workflow.md` and **embed its full content** in each teammate's spawn prompt. Teammates cannot access skill reference files — they only see what's in their prompt.
 
-Reference: `references/teammate-workflow.md` — include full workflow in each teammate's prompt.
+**Do NOT just reference the file.** Copy-paste the entire workflow into the prompt.
 
 **Summary:** Plan (`/ck:plan --hard`, opus) → `/clear` → Implement (`/ck:cook`, sonnet) → Commit → Push → Create PR
 
+## Step 4b: Plan Checkpoint (Lead Responsibility)
+
+After spawning teammates, lead MUST verify planning completes before implementation:
+1. Wait for teammate to send plan via `ExitPlanMode` (triggers approval request)
+2. Review the plan — check it exists in `plans/` directory
+3. **Approve** → teammate proceeds to implementation
+4. **Reject** → send feedback, teammate revises plan
+5. Do NOT approve if teammate skipped planning and jumped to code changes
+
 ## Step 5: Review Cycle
 
 Reviewer agent reviews each PR using `/ck:code-review`, `/ck:test`, `/ck:web-testing`.
@@ -70,7 +96,8 @@ Done when all assigned issues complete and no workable issues remain.
 - Issues needing human input: label `needs-human` on GitHub
 - Issues too complex without user plan: label `needs-planning` on GitHub
 - Shutdown all teammates via `SendMessage(type: "shutdown_request")`
-- Remove worktrees, call `TeamDelete`
+- Clean up worktrees: `node $HOME/.claude/skills/worktree/scripts/worktree.cjs remove <worktree-name-or-path>` for each dev/designer
+- Call `TeamDelete`
 
 ---
 
@@ -80,14 +107,15 @@ Every teammate prompt MUST end with:
 
 ```
 CK Context:
-- Work dir: {CWD}
+- Work dir: {worktree_path or CWD for reviewers}
 - Reports: plans/reports/
 - Plans: plans/
-- Branch: {current branch}
+- Branch: team-auto/{issue-number}-{slug}
 - Naming: YYMMDD-HHMM
 - Active plan: none
 - Commits: conventional (feat:, fix:, docs:, refactor:, test:, chore:)
 - Refer to teammates by NAME, not agent ID
+- IMPORTANT: All file operations and commands MUST run from your Work dir above
 ```
 
 ## Lead Behavior Rules

package/skill/references/lead-coordination-protocol.md

@@ -28,9 +28,20 @@ Add designer only if issues involve UI/UX work.
 
 For each issue → create TaskCreate with:
 - `subject`: "Implement #<number>: <title>"
-- `description`: Full issue body + role skills + teammate workflow reference
+- `description`: Full issue body + role skills + **full inline teammate workflow** (from `references/teammate-workflow.md`)
 - `owner`: assigned teammate name
 
+**CRITICAL:** Read `references/teammate-workflow.md` and embed its entire content in the teammate's spawn prompt. Teammates cannot access skill reference files — they only see what's in their prompt.
+
+### Plan Verification (MANDATORY)
+
+After spawning teammates (spawned with `mode: "plan"`):
+1. Teammate submits plan via `ExitPlanMode` → triggers approval request to lead
+2. Lead reviews plan: check it's saved in `plans/`, covers the issue scope
+3. **Approve** → teammate exits plan mode, proceeds to implementation
+4. **Reject with feedback** → teammate revises, resubmits
+5. **Never approve** if teammate skipped planning or has no plan file
+
 ### Monitoring Loop
 
 Event-driven via hooks:
@@ -79,5 +90,9 @@ Work done when:
 1. Verify all tasks completed
 2. `SendMessage(type: "shutdown_request")` to each teammate
 3. Wait for shutdown confirmations
-4. `TeamDelete` (no parameters)
-5. Report summary to user: issues completed, PRs merged, issues deferred
+4. Clean up worktrees for each developer/designer:
+   ```bash
+   node $HOME/.claude/skills/worktree/scripts/worktree.cjs remove <worktree-name-or-path>
+   ```
+5. `TeamDelete` (no parameters)
+6. Report summary to user: issues completed, PRs merged, issues deferred

package/skill/references/teammate-workflow.md

@@ -1,21 +1,28 @@
 # Teammate Workflow — Detailed Agent Flow
 
-## Phase 1: Planning (model: claude-opus-4-5-20251101)
+## Phase 1: Planning (MANDATORY — model: claude-opus-4-5-20251101)
+
+**You are spawned in `mode: "plan"` — you CANNOT edit files until your plan is approved by lead.**
 
 1. Receive assigned GitHub issue from lead
 2. Read issue details: `gh issue view <number> --json title,body,labels,comments`
-3. Activate `/ck:plan --hard` skill to create implementation plan
-4. During planning, if questions arise that need user confirmation:
+3. Read project README.md and relevant docs in `./docs/` for context
+4. Activate `/ck:plan --hard` skill to create implementation plan
+5. During planning, if questions arise that need user confirmation:
    - Send message to lead agent: `SendMessage(to: "lead", type: "message", content: "Question for user: <question>")`
    - Wait for lead to relay user's answer
-5. If issue/question cannot be handled by agent:
+6. If issue/question cannot be handled by agent:
    - Create GitHub issue: `gh issue create --title "<title>" --body "<details>" --label "needs-human"`
    - Notify lead
-6. Plan saved to `{plans_path}/` following naming convention
+7. Plan saved to `{plans_path}/` following naming convention
+8. Submit plan via `ExitPlanMode` — this sends plan to lead for approval
+9. **WAIT for lead approval before proceeding to Phase 2**
+
+**IMPORTANT:** Do NOT skip this phase. Do NOT attempt code changes during planning. The `mode: "plan"` enforcement will block file edits until approved.
 
 ## Phase 2: Context Reset
 
-After plan is complete:
+After plan is approved by lead (you'll receive approval message):
 1. Use `/clear` to clear context window
 2. This ensures maximum context available for implementation
 
@@ -62,7 +69,8 @@ If lead assigns conflict resolution:
 
 ## Worktree Notes
 
-- Each teammate works in isolated git worktree (via `isolation: "worktree"`)
-- Branch naming: `team-auto/<issue-number>-<slug>`
-- Worktree auto-created by Agent Teams infrastructure
-- On shutdown, lead ensures worktree cleanup
+- Lead creates your worktree BEFORE spawning you — your CK Context tells you the path
+- **All file reads, edits, and shell commands MUST use your worktree path** (provided in spawn prompt)
+- Branch naming: `team-auto/<issue-number>-<slug>` (already checked out in your worktree)
+- You are NOT in the main repo directory — `cd` to your worktree path at the start of every phase
+- On shutdown, lead handles worktree cleanup via `git worktree remove`