Help us improve
Share bugs, ideas, or general feedback.
From spex
DEPRECATED: Spawns teammates in isolated git worktrees to implement tasks from tasks.md, reviews against spec.md using spex:review-code, merges compliant changes. Use spex:teams-orchestrate instead.
npx claudepluginhub rhuss/cc-spex --plugin spexHow this skill is triggered — by the user, by Claude, or both
Slash command
/spex:teams-spec-guardianThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill implements the spec guardian pattern for the `teams-spec` trait. The lead session does not implement any tasks. Instead, it:
Orchestrates parallel task implementation via Claude Code Agent Teams: analyzes tasks.md dependencies, spawns isolated git worktrees per group, reviews via spec guardian before merging.
Executes implementation plans from spec files: detects mode (sequential, delegated, team) from YAML frontmatter, creates git feature branches, manages task dependencies, dispatches agents, runs validations/hooks.
Use when a task benefits from multiple Claude instances collaborating with peer-to-peer messaging - parallel research, multi-module features, cross-layer changes, or competing hypothesis debugging. Not for simple independent tasks (use parallel-execution) or sequential tasks (use delegated-execution).
Share bugs, ideas, or general feedback.
This skill implements the spec guardian pattern for the teams-spec trait. The lead session does not implement any tasks. Instead, it:
This skill supersedes spex:teams-orchestrate when both teams-vanilla and teams-spec traits are active. Check .specify/spex-traits.json for teams-spec: true to confirm this skill should run.
Same as spex:teams-orchestrate: read tasks.md, identify independent task groups, determine parallel opportunities.
Each teammate gets its own git worktree for file isolation.
isolation: "worktree" or instruct the teammate to use the EnterWorktree tool)Each teammate receives:
You are implementing tasks for the [feature-name] feature.
You are working in an isolated git worktree.
## Your Assigned Tasks
[List the specific tasks assigned to this teammate with bd issue IDs]
## Spec Context
[Contents of spec.md for this feature]
## Working Rules
1. Implement each task completely before moving to the next
2. Commit after each task with a descriptive message
3. When all your tasks are done, message the lead: "Tasks complete, ready for review"
4. If you encounter a blocker, message the lead with details
5. Do not modify files outside your assigned task scope
6. Your work will be reviewed against spec.md before merging
The lead monitors teammates and reviews their work as they complete tasks.
Review the changes: Examine the teammate's worktree diff against the working branch
Run spec compliance check: Invoke {Skill: spex:review-code} against the teammate's changes, checking compliance with spec.md
Decision:
If review PASSES:
[X])If review FAILS:
If a teammate repeatedly fails review (3+ attempts on the same task):
When all tasks are complete and merged: