dogfood

Identify and document web application bugs through structured exploratory QA testing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AVOI-CEO/avoi-agent --skill dogfood-avoi-ceo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/AVOI-CEO/avoi-agent/tree/main/skills/dogfood
Command: npx skills add https://github.com/AVOI-CEO/avoi-agent --skill dogfood-avoi-ceo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web applications often have subtle bugs that are hard to reproduce without a structured testing approach. This skill provides a repeatable workflow to systematically explore, capture evidence, and report issues.

Core Features & Use Cases

  • Systematic exploratory QA testing of web applications using the browser toolset to navigate, interact with elements, and observe behavior.
  • Evidence capture and documentation, including annotated screenshots and structured bug reports for faster triage.
  • End-to-end dogfood workflow: planning, exploration, evidence collection, issue categorization, and formal reporting.

Quick Start

Plan an exploratory QA session, navigate the target site with the browser toolset, capture evidence, and generate a structured bug report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform systematic exploratory QA testing on a web application?▼

Exploratory QA testing of web apps requires a browser toolset to navigate targeted pages, interact with elements, observe edge cases, and capture annotated screenshots to document bugs. This structured approach ensures subtle issues are reproducible and formally reported for faster triage.

How do I capture evidence and generate a structured bug report during web app testing?▼

To capture evidence and generate a structured bug report during web app testing, use a browser toolset to trigger edge cases, take annotated screenshots, categorize the issues, and compile them into a formal dogfood report.

What is the best way to structure an exploratory QA session for uncovering hard-to-reproduce bugs?▼

The best way to structure an exploratory QA session for uncovering hard-to-reproduce bugs is to follow a defined workflow: plan the testing scope, explore user flows, collect evidence, categorize issues, and produce a formal dogfood report.

Do I need a predefined testing plan to start finding bugs in web applications?▼

Yes, you need a predefined testing plan to systematically explore targeted pages and edge cases. A structured plan guides the browser toolset interactions and ensures the final bug report is comprehensive and reproducible.

What limitations exist when using a browser toolset for exploratory web app testing?▼

Limitations of exploratory web app testing with a browser toolset include the inability to test backend APIs or non-web interfaces, as the workflow specifically focuses on navigating web pages, interacting with UI elements, and capturing frontend evidence.