agent-team-pipeline

Plugin agent-team-pipeline from marketplace neoeinstein-plugins in neoeinstein/claude-plugins. Commands read from the repo's manifest — 3 days ago.

Skills (1)

• orchestrate-pipeline

  Use when coordinating multi-agent development pipelines with phased investigation, planning, implementation, and review. Orchestrates teams of specialized agents through gated phases. Language-agnostic.

Subagents (10)

• codebase-investigator

  Use this agent for Phase 1 investigation when the task requires codebase exploration — systematically catalogs the current state of a concern. Searches for patterns, construction sites, and edge cases. Returns a structured findings report.

• combined-researcher

  Use this agent for Phase 1 investigation when the task requires both codebase exploration AND external knowledge — e.g., understanding current implementation then researching how an API or library actually works. Returns a unified findings report.

• evaluator

  Use this agent for Phase 6 code quality evaluation — reviews implementation for code quality, security, type safety, or other concerns. Dispatched with a specific evaluator prompt from the project's evaluator configuration. Runs AFTER spec compliance passes.

• fixer

  Use this agent to address specific findings from evaluators or spec-reviewers that indicate spec compliance or quality failures. Input is a set of findings with file:line references. Must re-run verification after fixes and report what was changed.

• implementor

  Use this agent to implement a specific task from a plan. Follows the plan exactly, writes tests, self-reviews, commits, and reports back with evidence. Dispatched once per task — fresh agent each time to prevent context pollution.

• internet-researcher

  Use this agent for Phase 1 investigation when the task requires external knowledge — API documentation, library usage patterns, current best practices, or technology comparisons. Returns a structured findings report with sources.

• plan-validator

  Use this agent for Phase 3 plan validation — independently verifies that a plan is correct, complete, and safe to implement. Reads the actual codebase to verify the planner's claims.

• planner

  Use this agent for Phase 2 planning — takes investigation findings and produces an actionable change plan with exact file:line specifications. Every change must be specific enough for an implementor with no project context to execute.

• remote-code-researcher

  Use this agent when you need to understand how an external library or open-source project implements a feature by examining actual source code. Clones the repo, investigates with codebase analysis, and reports with file:line citations.

• spec-reviewer

  Use this agent after implementation completes to verify the implementation matches its specification. Compares actual code changes against the planned changes — does NOT trust the implementor's report. Must be dispatched BEFORE code quality evaluators.

Hooks (1)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/detect-pipeline-config.sh"

Similar plugins