UI Aqa Flow

<ui_aqa_flow>

<description_and_purpose>

End-to-end test automation from requirements gathering to test implementation. Uses test cases, project documentation to create automated tests following existing architecture and coding standards.

Prerequisite: Rosetta Prep Steps.

Terminology. External systems are named by role throughout this workflow and its phases: Test Management System (TMS), Issue Tracker, and Wiki. TestRail, Jira, and Confluence are canonical examples only — adapt identifiers, URLs, requests, calls, and query syntax to the systems resolved for the current project (from repository-root gain.json, explicit user input, recognizable URLs/handles, and available integrations).

</description_and_purpose>

<workflow_phases>

Execution cadence:

• All Rosetta prep steps MUST be FULLY completed
• USE SKILL load-project-context, orchestration, hitl
• MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
• Execute every in-scope phase in strict 1-8 order (never skip without explicit HITL confirmation): APPLY PHASE the phase file → update agents/TEMP/<FEATURE>/ui-aqa-state.md → next; never start a phase until the previous is marked done in ui-aqa-state.md.
• MUST follow JIT phase-by-phase: do not load/act IN ADVANCE.
• Skip gates, transitions, and escalation → <orchestration_and_escalation>.
• MUST ALWAYS use todo tasks ledger, ASAP. Prioritize ACCURACY over SPEED. Proactively use available tools/MCPs, if question can be answered from code or MCP call - do that first.

No assumptions:

• NO ASSUMPTIONS: never assume selectors, flows, or data — ask the user when information is missing.

Customization:

• If the user gave no preferences, perform all steps except optional.
• User CAN customize specific phases / already-done phases / goals / cases — LISTEN and ADOPT.

Authoritative rules (do not skim past):

• USE SKILL coding before any work touching repository tests, page objects, or shared helpers — authoritative for conventions; repository docs win over skill snippets.
• Default: reuse existing page objects/tests first; create new files only when no suitable match exists.
• Explicit assertions: every test validation traces to a requirement — owned by Phase 2 (### Explicit Assertions in the test plan), enforced when Phase 6 implements tests.
• Blocking infeasibility = HARD-STOP + HITL (NOT waived by a clarification skip): if any phase finds the feature/elements under test do not exist such that the test cannot be authored without inventing selectors/flows/data or modifying product source, STOP and escalate with the options — point at the real feature/URL · author the missing UI as a separate approved task · a clearly-marked pending/fixme spec · abort — and WAIT for the user's explicit choice. "Skip clarification" waives clarification questions only; it never authorizes this feasibility/scope call.

<data_collection phase="1" applies="ALL" subagent="discoverer" role="UI-AQA data collector" subagent_required_model="gpt-5.6-terra-medium">

• APPLY SKILL FILE phases/ui-aqa-flow-data-collection.md
• Input: user request + repository-root gain.json + project context at its configured paths (canonical: docs/CONTEXT.md, docs/ARCHITECTURE.md, agents/IMPLEMENTATION.md). Output: test plan at plans/ui-aqa-<test-name>/test-plan.md
• Required skills: data-collection, sensitive-data, qa-structure, qa-knowledge