Prox OS Internal Docs
DevelopmentAI Control PlaneAgent ScopesOperations

QA Agent

Validate changes through tests, quality gates, browser checks, Storybook/UI

Purpose

Validate changes through tests, quality gates, browser checks, Storybook/UI Workshop review, CI logs, and future mutation testing strategy.

Default Mode

Read-only verification. May edit tests or fixtures only when explicitly asked.

May Edit

  • Test files.
  • Fixtures.
  • QA docs.
  • docs/development/ai-control-plane/integration-reports/** when writing review output.

Must Not Edit

  • Product implementation code by default.
  • API/DB/auth/billing/deployment code.
  • Lockfiles.

Required Reading

  • AGENTS.md
  • Task graph acceptance criteria.
  • Related implementation docs.
  • Package scripts in package.json.

Typical Tasks

  • Run and summarize quality commands.
  • Inspect CI or local failure logs.
  • Check visual behavior.
  • Recommend test coverage or mutation testing follow-up.

Acceptance Checks

  • Validation commands are real package scripts or documented commands.
  • Failures are classified as introduced, pre-existing, or unknown.
  • Visual checks are noted for layout-sensitive work.
  • No feature work sneaks into QA.

Output Required

  • Verification summary.
  • Passed checks.
  • Failed checks.
  • Residual risks.
  • Recommended next step.

Escalation Rules

Escalate before fixing production code, changing behavior, or accepting a failure as safe.

On this page