Agent workflows

Once VisualQ MCP is installed (quick start), use these workflows in Cursor or Claude Code Agent mode.

Workflow 1 — Pre-merge PR gate

Goal: Decide if a PR can merge based on VRT + FRT + rolling health.

1. Use MCP prompt pr-quality-gate, or say:

   Run prompt pr-quality-gate for project acme-shop on staging.

2. The agent calls gate_pr_quality and returns blockMerge: true/false.

3. If blocked:

   • VRT: get_run_failures → explain_vrt_failure
   • FRT: frt_explain_failure
   • Re-run after fixes: run_vrt with confirm: true

4. Open viewerUrl in the response to see diffs in the dashboard.

Workflow 2 — Run VRT from the IDE

Run VRT on staging for project acme-shop, wait for completion, and list failures with mismatch %.

Agent sequence:

1. run_vrt (confirm: true, environment: staging, project: acme-shop)
2. wait_for_run
3. get_run_failures
4. Optional: explain_vrt_failure on the worst scenario

Workflow 3 — Create an FRT journey from plain language

Use prompt frt-journey-from-goal or:

Create an FRT test: user logs in, adds a product to cart, and reaches checkout.
Start URL: https://staging.example.com/
Project: acme-shop

Agent sequence:

1. frt_search_step_library
2. frt_propose_journey → poll get_job_status
3. frt_save_feature_draft (confirm: true)
4. frt_compile_feature
5. run_frt_feature (confirm: true)

Set VISUALQ_TOOL_PROFILE=frt-qa for a focused toolset.

Workflow 4 — Onboard a new client site

Use prompt onboard-new-site:

Onboard https://new-client.com/ in VisualQ — crawl, baselines, and one critical FRT flow.

Steps the agent follows:

create_project → crawl_site → generate_scenarios → run_baseline → frt_propose_journey → check_setup_health

Workflow 5 — Jira ticket coverage

Use prompt jira-qa:

Cover JIRA ticket PROJ-456 for project acme-shop: acceptance criteria are login + order history visible.

The agent creates or updates VRT or FRT coverage, runs tests, and summarizes with gate_pr_quality.

Workflow 6 — Setup health review

Before a release or after config changes:

Run prompt setup-health-review for project acme-shop.

Surfaces missing baselines, unconfigured environments, and FRT compile blockers via check_setup_health.

Confirm mutations explicitly

Tools that change state (run tests, approve baselines, save FRT drafts) require confirm: true. Tell your agent “yes, confirm” when prompted — this prevents accidental runs.

Related

• Quick start for agents
• MCP reference
• Agent setup (install paths)
• FRT writing features