Development

Audits existing tests for risk coverage, reliable oracles and maintenance value; does not edit tests.

Audits cross-cutting codebase health, security and maintainability; not a single-change review or specialist audit.

Audits documentation and comments for trust, coverage, consistency and freshness; read-only.

Reviews a completed change for acceptance, regressions and release risk; read-only, not a whole-codebase audit.

Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.

Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code.

Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.

Evaluates new product opportunities through demand, channels and economics before committing to build.

Evaluates observed product outcomes against a prior hypothesis; does not run experiments or change user treatment.

Diagnoses incidents from operational evidence and proposes recovery; does not change live systems.

Compares tools or implementations through controlled benchmarks and independent correctness checks.

Profiles and improves a measured performance bottleneck; retains only verified improvements.

Modernizes a bounded capability to reduce demonstrated maintenance cost; not routine upgrades or performance tuning.

Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.

Implements one scoped feature or fix through the smallest complete solution; not upgrades or performance tuning.

Prepares CI/CD and infrastructure, then executes authorized deployments with health and recovery checks.

Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications.

Commits, pushes and remotely verifies authorized repository changes; does not create releases.

Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only.

Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.

Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.

Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.

Creates evidence-backed current or target architecture diagrams; not UI design.

Records one architecture decision with alternatives, consequences and status; does not design the whole system.