agent-team

Plugin agent-team from marketplace engineering-standards-marketplace in shah-arnav3/eng_standards-marketplace-claudecode. Commands read from the repo's manifest — 6 days ago.

Skills (1)

• ship

  Runs the agent-team delivery pipeline end to end — Architect, Software Engineer, Reviewer, QA Test Generator, CI/CD Orchestrator, and optionally DevOps and SRE/Monitoring — routing each stage's output to the next through files, enforcing retry limits, and stopping for human approval at the design an

Subagents (7)

• architect-agent

  Consumes a PRD (product requirements document) and produces a Technical Design Document — data structures, API schemas, and the step-by-step logic flow the engineer agent must follow. Use proactively at the start of any feature/project build, before any code is written, whenever a PRD, feature spec,

• cicd-orchestrator-agent

  Executes code in a sandbox environment and runs the test suite, interprets terminal error output, and — on failure — captures the stack trace and returns it with fix instructions for the Software Engineer Agent. Use after the QA Test Generator Agent has produced a test suite, or any time code needs

• devops-agent

  Packages the application and handles cloud infrastructure — generates Dockerfiles, writes Terraform or Kubernetes configuration, and, with explicit human approval, executes deployments to staging/production. Use once the CI/CD Orchestrator Agent reports a passing build, or whenever infrastructure/pa

• qa-test-generator-agent

  Reads the code and the PRD's acceptance criteria to write automated unit and integration tests using frameworks like PyTest, Jest, or Playwright, deliberately trying to break the Software Engineer Agent's code. Use after the Reviewer Agent has approved code (or in parallel, if the pipeline runs revi

• reviewer-agent

  Critiques the Software Engineer Agent's code before it goes to testing — reviews for readability, edge-case bugs, security vulnerabilities, and adherence to the Technical Design Document. Use proactively immediately after new or changed code is written and before the QA Test Generator Agent runs, or

• software-engineer-agent

  Reads a Technical Design Document and writes the actual source code — creates files, installs packages, and writes modular functions matching the design. Use after a Technical Design Document exists and code needs to be written or an existing implementation needs to be extended to match a design.

• sre-monitoring-agent

  Watches the live system — parses logs and error-tracking/metrics data (like Sentry or equivalent), alerts the team if error rates spike, and recommends a rollback for a human to approve. Read-only: it never deploys or rolls back itself. Use once the DevOps Agent has deployed a change to staging or p

Hooks (1)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/confirm-deploy.sh"

Similar plugins