dream-team

Plugin dream-team from marketplace dream-team-marketplace in Ratler/dream-team-marketplace. Commands read from the repo's manifest — 28 days ago.

Skills (5)

• debug

  Use when encountering a bug, test failure, unexpected behavior, or when the user asks for help debugging. Hypothesis-driven — reproduce, investigate, fix, verify. Standalone — works outside the plan/spec/build workflow.

• plan

  Start here — use when the user wants to build something new or plan a feature. Collaborative brainstorming that explores requirements, constraints, and approach through natural dialogue before any spec is written.

• spec-delegated

  Use after /dream-team:plan to write a delegated execution spec (orchestrator + sub-agents). No arguments needed — picks up conversation context from the brainstorming session.

• spec-sequential

  Use after /dream-team:plan to write a sequential execution spec. No arguments needed — picks up conversation context from the brainstorming session.

• spec-team

  Use after /dream-team:plan to write a team execution spec (parallel Claude instances). No arguments needed — picks up conversation context from the brainstorming session.

Slash commands (1)

• /dream-team:progress

  Show build progress for a spec

Subagents (12)

• MANIFEST
• architect

  Use this agent for design decisions, architectural analysis, solution proposals, and structural recommendations. Read-only — produces designs, not code.

• builder

  Use this agent when code needs to be written, files created, or features implemented. Executes ONE task at a time with full read/write access. Uses TDD. Follows specs exactly.

• debugger

  Use this agent for systematic debugging. Reproduces issues, forms hypotheses, investigates root causes, applies targeted fixes, and verifies resolution. Interactive and methodical — understand it before fixing it.

• docs

  Use this agent after all code is written to produce and update project documentation. Reviews changes against the spec's Documentation Requirements section and writes README updates, changelog entries, API docs, and inline comments for complex logic. Read-write — modifies documentation files only.

• merger

  Use this agent for branch integration in delegated mode. Merges builder worktree branches back into the feature branch with tiered conflict resolution. Dispatched by the orchestrator after builder completion and review approval.

• researcher

  Use this agent for codebase exploration, documentation research, pattern investigation, and gathering context. Read-only — cannot write or edit files.

• reviewer

  Use this agent for qualitative code review against specs and coding standards. Categorizes issues by severity. Read-only — cannot modify files.

• scout

  Use this agent for fast, cheap pre-build reconnaissance. Scans file structures, identifies patterns and conventions, reports gotchas. Read-only — sonnet model, since its findings steer builders on complex tasks. Dispatched by the orchestrator before builders on complex tasks.

• security-reviewer

  Use this agent for proactive security auditing of code changes. Works through a structured 7-category checklist on every review. Read-only — cannot modify files.

• tester

  Use this agent for independent adversarial testing, integration tests spanning multiple components, and security/boundary testing. Writes test files only — cannot modify source code. Complements builder TDD by testing from the spec (not the implementation) and targeting edge cases builders miss.

• validator

  Use this agent for final mechanical verification. Runs validation commands, checks acceptance criteria, produces pass/fail report. Read-only.

Hooks (5)

• SessionStart

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session_start.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/preflight_team_check.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/block_nested_agent.js

• TaskCompleted

  node ${CLAUDE_PLUGIN_ROOT}/hooks/validate_task_completed.js

• PostCompact

  node ${CLAUDE_PLUGIN_ROOT}/hooks/postcompact_checkpoint.js

Similar plugins