dogfood

Guide browser-based exploratory QA with a five-phase workflow and structured reports.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/linfordWu/owls --skill dogfood-linfordwu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/linfordWu/owls/tree/main/skills/dogfood
Command: npx skills add https://github.com/linfordWu/owls --skill dogfood-linfordwu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Dogfood skill guides systematic exploratory QA testing of web applications to uncover bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

  • Structured QA workflow: Plan, Explore, Collect Evidence, Categorize, and Report.
  • Evidence capture: Screenshots, console logs, and issue taxonomy to support bug reports.
  • Automated reporting: Produce a comprehensive Dogfood QA report with an evidence trail and reproducible steps.

Quick Start

Run a 2-page exploratory QA pass on the target site and generate a dogfood-output report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
What is exploratory QA testing and how does it capture bug evidence?

Exploratory QA testing systematically navigates web applications to uncover bugs, capturing screenshots and console logs as evidence. This structured approach compiles findings into a comprehensive report with an issue taxonomy and reproducible steps.

How do I run systematic exploratory testing on a single-page web app?

Run systematic exploratory testing on a single-page web app by following a five-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. This process generates an evidence trail and a final structured QA report.

Can I use this structured QA workflow for full-site regression runs?

Yes, you can use this structured QA workflow for full-site regression runs. It applies to both single-page apps and multi-page sites, supporting testing scopes from page-level checks to comprehensive site-wide regression testing.

What's the best way to compile a structured bug report with console logs and screenshots?

The best way to compile a structured bug report is through an automated five-phase QA workflow that captures screenshots and console logs. It categorizes issues using a taxonomy and outputs a final report with a complete evidence trail.

What testing scopes are supported for multi-page web applications?

Supported testing scopes for multi-page web applications range from targeted page-level checks to full-site regression runs. The workflow systematically guides exploration, evidence collection, and reporting across all defined scopes.