engineering-team

Plugin engineering-team from marketplace engineering-team-dev in daeon/EngineeringTeam. Commands read from the repo's manifest — 1 month ago.

Skills (1)

• engineering-team

  Use for non-trivial software and repository work requiring evidence-gated implementation or read-only investigation, including codebase analysis, debugging and root cause, logs and incidents, performance, architecture or PR review, security, migration, release and rollback, and engineering-task hand

Subagents (11)

• advisor-consultant

  Independent read-only advisor for risk gates. Use when the lead needs a second opinion on uncertain architecture, unclear root cause, conflicting evidence, security, migration, compatibility, release, production-sensitive, broad multi-file, or assumption-heavy completion decisions.

• codebase-investigator

  Investigates repositories to create repo atlases, component briefs, symbol maps, test maps, configs, runtime paths, generated-code rules, and evidence before code changes.

• dx-documentation-reviewer

  Reviews developer experience, documentation, CLI behavior, error messages, onboarding, examples, and public-facing guidance for software changes.

• evidence-skeptic

  Challenges software engineering claims by requiring evidence, falsifying hypotheses, checking contract graphs and test validity, identifying unsupported assumptions, and blocking premature implementation.

• implementation-engineer

  Proposes and implements the smallest safe code change after investigation, architecture/security/performance constraints, verification planning, and evidence review.

• migration-analyst

  Reviews migrations across versions, products, APIs, schemas, configuration formats, and legacy systems, focusing on semantic compatibility and edge cases.

• optimization-engineer

  Reviews performance, latency, throughput, memory, CPU, IO, concurrency, caching, algorithmic complexity, profiling, benchmark validity, polling, wakeups, and resource limits.

• release-rollback-engineer

  Reviews deployment, rollout, observability, feature flags, operational safety, migration safety, production behavior, and rollback paths for software changes.

• security-analyst

  Reviews software changes for realistic security risks including trust boundaries, auth, authorization, input validation, injection, secrets, unsafe shell/filesystem/network behavior, data exposure, privilege boundaries, and dependency risk.

• system-design-architect

  Reviews software architecture, system boundaries, abstractions, interfaces, dependency direction, scalability, maintainability, and long-term design risks.

• test-verification-engineer

  Designs and runs verification plans for software changes, including unit, regression, integration, security, performance, migration, manual checks, and failure attribution.

Similar plugins