dogfood

Automate exploratory QA testing of web applications with a five-phase workflow.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill dogfood-rawgrowth-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Rawgrowth-Consulting/rawclaw-agent/tree/main/skills/dogfood
Command: npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill dogfood-rawgrowth-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications to uncover bugs, collect evidence, and generate structured reports.

Core Features & Use Cases

  • Browser-driven exploration: navigate, interact, and capture evidence across web pages.
  • Five-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report to produce repeatable QA results.
  • Evidence-rich reporting: auto-generated screenshots, logs, and a final bug report suitable for handoff.

Quick Start

Provide a target URL and testing scope, then run the dogfood workflow to generate a structured QA report.

Frequently Asked Questions about dogfood

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate exploratory QA testing for web applications?

Automated exploratory QA testing for web apps uses a structured five-phase workflow to navigate pages, interact with elements, and capture evidence. It systematically plans, explores, collects, categorizes, and reports bugs for repeatable results.

What is structured exploratory testing and when do I need it for web apps?

Structured exploratory testing systematically uncovers bugs across multi-page web apps using a browser toolset. You need it for manual QA workflows, regression checks, and pre-deployment testing to generate evidence-backed bug reports.

Can I generate bug reports with screenshots for pre-deployment web testing?

Yes, pre-deployment web testing generates evidence-rich bug reports with auto-captured screenshots and console logs. The workflow collects evidence during browser exploration and categorizes issues for a structured handoff report.

Do I need a browser toolset to run automated QA testing on web apps?

Yes, automated QA testing requires a browser toolset with navigate, snapshot, click, type, vision, and console capabilities. These tools enable the browser-driven exploration needed to interact with web pages and collect bug evidence.

What's the best way to collect evidence during browser-driven QA testing?

The best way to collect evidence during browser-driven QA testing is following a structured workflow that auto-generates screenshots and logs. The collection phase captures visual and console data during exploration before categorizing issues for reporting.