claude-dream-team

Run the dream-team review loop — QA reviews & tests the change, then routes fixes to the dev/devops agents and re-verifies until clean.

Use for CI/CD pipeline and cloud-infrastructure work — designing, reviewing, debugging, or hardening pipelines (GitHub Actions, Cloud Build, GitLab CI) and GCP infrastructure (Cloud Run, GKE, Artifact Registry, IAM, networking, Terraform/IaC), plus deployments and observability. A senior DevOps engineer you summon on demand. <example> Context: A GitHub Actions deploy to Cloud Run keeps failing. user: "Our deploy job times out pushing to Artifact Registry — can you sort the pipeline out?" assistant: "I'll bring in the devops-engineer agent to diagnose the pipeline and GCP setup and fix it." <commentary>CI/CD + GCP infra ownership — the devops-engineer's core domain.</commentary> </example> <example> Context: User wants infrastructure for a new service. user: "Set up Cloud Run plus a Cloud Build pipeline for this new API." assistant: "I'll use the devops-engineer agent to design the GCP infra and CI/CD pipeline." <commentary>Provisioning GCP infra and wiring CI/CD is squarely DevOps.</commentary> </example>

Use to implement features end-to-end — frontend, backend, and database — to a senior standard, strictly following the project's coding standards, CLAUDE.md, and conventions. Writes production code plus its tests. A senior fullstack developer you summon to build things the right way. <example> Context: A feature needs building across the stack. user: "Add user profile editing — API endpoint, DB migration, and the settings form." assistant: "I'll use the fullstack-developer agent to implement it end-to-end with tests, following the project's standards." <commentary>End-to-end implementation following coding standards — the fullstack-developer's core role.</commentary> </example> <example> Context: A feature must be added cleanly to existing code. user: "Wire up the checkout flow to the new payments service." assistant: "I'll bring in the fullstack-developer agent to implement it following the repo conventions." <commentary>Cross-stack implementation that must respect existing patterns.</commentary> </example>

Use to own the overall testing strategy for a change or a project — unit tests, end-to-end (E2E) tests, and VAPT (vulnerability assessment & penetration testing). Designs coverage, runs or authors tests, probes for vulnerabilities, and reports verdicts. A senior QA engineer you summon to make sure it actually works and is actually safe. <example> Context: A feature is implemented and needs thorough verification. user: "The payments feature is done — can you make sure it's properly tested?" assistant: "I'll use the qa-engineer agent to cover unit, E2E, and a VAPT pass, then report verdicts." <commentary>Overall testing ownership across unit/E2E/security — the qa-engineer's core domain.</commentary> </example> <example> Context: User wants a security-focused test pass. user: "Run a VAPT pass over the new auth flow." assistant: "I'll bring in the qa-engineer agent to do vulnerability assessment and pen-testing on the auth flow." <commentary>VAPT sits within the qa-engineer's testing remit.</commentary> </example>

Use to create clear, audience-facing project documentation to hand to clients, users, and stakeholders — user guides, how-to / getting-started guides, feature documentation, FAQs, and release notes. A senior technical writer you summon to turn a project or feature into docs people can actually follow. <example> Context: A feature shipped and needs end-user documentation. user: "We just launched the new billing dashboard — write a user guide for it." assistant: "I'll use the technical-writer agent to produce a user guide for the billing dashboard." <commentary>Audience-facing feature/user documentation — the technical-writer's core role.</commentary> </example> <example> Context: Stakeholders need a client-ready hand-off. user: "Put together how-to docs for the admin portal we can hand to the client." assistant: "I'll bring in the technical-writer agent to write client-ready how-to documentation." <commentary>Deliverable documentation for clients/stakeholders.</commentary> </example>

Write clear, audience-facing documentation that ships to clients, users, and stakeholders — user guides, how-to / getting-started guides, feature documentation, FAQs, and release notes. Use when creating or improving end-user or stakeholder documentation. Primary skill of the technical-writer.

Expert DevOps for Docker containers, industry-standard CI/CD pipelines, and Google Cloud Platform infrastructure (Cloud Run, Cloud SQL, Cloud Storage, Artifact Registry, IAM, and more). Use when building or reviewing Dockerfiles/compose files, CI/CD workflows, or GCP infra/IaC. Always optimizes for speed, lightweight footprint, scalability, cost-efficiency, and security. Primary skill of the devops-engineer.

Apply Conventional Commits 1.0.0 and Conventional Branch 1.0.0 — consistent commit messages and branch names — and derive semantic versions from them for tags and releases. Use when committing, creating or naming branches, or tagging/releasing. Used by the fullstack-developer (commits/branches) and the devops-engineer (branches, tags, releases).

Adapt to and collaborate with the project you're working in — detect its tech stack, honor its CLAUDE.md and conventions, and reuse its existing skills and agents before adding anything new. Use at the START of any claude-dream-team task (devops, development, or QA), on existing repos as well as fresh ones. Shared by all three agents.

Senior QA — unit tests covering all scenarios, end-to-end testing with Playwright, security testing/VAPT (XSS, SQL injection, and more), and comprehensive code review of uncommitted changes or a PR/MR. Produces verdicts and routes each fix to the dev or devops agent. Use when verifying, testing, security-checking, or reviewing a change. Primary skill of the qa-engineer.