Firecrawl QA
Use this to test a live site and return a unified QA report.
Onboarding Interview
Infer the URL, QA focus, and output format from context. If the target URL is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the URL, the focus area, or credentials/constraints for protected flows.
Firecrawl Collection Plan
Use Firecrawl map to discover pages. Use Firecrawl browser for interactions, forms, navigation, and responsive/manual checks when available. Use scrape for page content and link extraction.
Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners:
- Full: Navigation and Links, Forms and Interactions, Content and Visual, Error States.
- Forms: Form Discovery, Happy Path, Edge Cases, Validation.
- Navigation: Sitemap, Nav Testing, Link Checker, Routing.
- Responsive: Desktop, Tablet, Mobile, Interaction.
- Performance: Page Load, Asset Audit, Content Efficiency, Comparison.
Each tester should return severity, URL, description, evidence, and reproduction steps.
Final Deliverable
# QA Report: [Site]
## Summary
- Health score: [x/10]
- Pages tested: [count]
- Issues found: [critical/major/minor]
## Critical Issues
[C-1] URL | Description | Steps to reproduce | Expected vs actual
## Major Issues
[M-1] URL | Description | Steps to reproduce
## Minor Issues
[m-1] URL | Description
## Positive Observations
[What works well]
## Pages Tested
[URLs]
## Agent/Test Summary
[Who tested what]
## Rerun Inputs
workflow: firecrawl-qa
url: [url]
focus: [full/forms/navigation/responsive/performance]
Quality Bar
- Include reproduction steps for functional issues.
- Do not report speculative bugs without evidence.
- Deduplicate findings across testers.
1---2name: firecrawl-qa3description: QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.4license: ISC5---67# Firecrawl QA89Use this to test a live site and return a unified QA report.1011## Onboarding Interview1213Infer the URL, QA focus, and output format from context. If the target URL is clear, proceed immediately.1415Ask at most 1-3 concise questions only if blocked, such as the URL, the focus area, or credentials/constraints for protected flows.1617## Firecrawl Collection Plan1819Use Firecrawl map to discover pages. Use Firecrawl browser for interactions, forms, navigation, and responsive/manual checks when available. Use scrape for page content and link extraction.2021## Parallel Work2223If appropriate, use sub-agents or equivalent parallel task runners:2425- Full: Navigation and Links, Forms and Interactions, Content and Visual, Error States.26- Forms: Form Discovery, Happy Path, Edge Cases, Validation.27- Navigation: Sitemap, Nav Testing, Link Checker, Routing.28- Responsive: Desktop, Tablet, Mobile, Interaction.29- Performance: Page Load, Asset Audit, Content Efficiency, Comparison.3031Each tester should return severity, URL, description, evidence, and reproduction steps.3233## Final Deliverable3435```markdown36# QA Report: [Site]3738## Summary39- Health score: [x/10]40- Pages tested: [count]41- Issues found: [critical/major/minor]4243## Critical Issues44[C-1] URL | Description | Steps to reproduce | Expected vs actual4546## Major Issues47[M-1] URL | Description | Steps to reproduce4849## Minor Issues50[m-1] URL | Description5152## Positive Observations53[What works well]5455## Pages Tested56[URLs]5758## Agent/Test Summary59[Who tested what]6061## Rerun Inputs62workflow: firecrawl-qa63url: [url]64focus: [full/forms/navigation/responsive/performance]65```6667## Quality Bar6869- Include reproduction steps for functional issues.70- Do not report speculative bugs without evidence.71- Deduplicate findings across testers.
om-scogo