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
Quality Bar
- Include reproduction steps for functional issues.
- Do not report speculative bugs without evidence.
- Deduplicate findings across testers.


