spec-team

Convert brainstorming context into a formal team-spec for parallel Claude Code agents.

16|3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Ratler/dream-team --skill spec-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-team
Source: https://github.com/Ratler/dream-team/tree/main/skills/spec-team
Command: npx skills add https://github.com/Ratler/dream-team --skill spec-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert brainstorming into a formal, executable team-spec that enables multiple Claude Code agents to work in parallel with a shared task list and mailbox-style communication.

Core Features & Use Cases

  • Formalizes brainstorming into a structured team spec with mode=team and spec-version:1, including Team Configuration and Review Policy sections.
  • Coordinates parallel agents to execute a plan without conflicting edits.
  • Supports optional design-related flags (playwright, frontend-design) and ensures guardrails like Tests, Deliverables, and cleanup.

Quick Start

Complete brainstorming with /dream-team:plan, then run /dream-team:spec-team to generate a parallel-team execution spec for multiple Claude Code agents.

Frequently Asked Questions about spec-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate parallel Claude Code agents to execute tasks without conflicting edits?

Parallel Claude Code agents are coordinated by generating a formal team-spec containing a shared task list and mailbox-style communication, ensuring independent execution without conflicts. The spec formalizes architecture planning and collaboration across multiple agents.

What is a team-spec for parallel agents and when do I need one?

A team-spec is a formal, deployable markdown document that enables multiple Claude Code agents to work in parallel. You need one when converting brainstorming context into structured execution plans with shared task lists and mailbox communication for coordinated team execution.

How to convert brainstorming context into a formal spec for Claude Code agents?

Brainstorming context is converted into a formal spec by applying frontmatter requirements like mode=team and spec-version:1, adding Team Configuration and Review Policy sections, and saving to specs/YYYY-MM-DD-<name>.md. This structured file enables parallel agent execution.

Does the generated team-spec support frontend design and playwright testing flags?

The generated team-spec supports optional design-related flags including playwright and frontend-design. These flags ensure appropriate guardrails such as Tests, Deliverables, and cleanup are included for frontend or browser automation tasks.

Can I use this spec template for architecture planning across multiple independent agents?

Yes, the spec template is designed for architecture planning and collaboration across independent agents. It coordinates shared task lists and mailbox-style communication, allowing multiple Claude Code agents to execute an architecture plan in parallel.

What frontmatter requirements does a parallel team execution spec need to satisfy?

A parallel team execution spec needs frontmatter satisfying mode=team and spec-version:1 requirements, along with optional playwright and frontend-design flags. It also requires Team Configuration and Review Policy sections to ensure proper agent guardrails.