dogfood

Automate exploratory QA testing of web applications and generate bug reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often suffer from hidden bugs that are only revealed through exploratory testing. This skill provides a structured approach to identifying, documenting, and evidencing issues during QA sessions.

Core Features & Use Cases

  • Systematic exploratory QA testing of web apps using a browser toolset to navigate, interact with elements, and capture evidence.
  • Generate a structured bug report from observed issues, including steps to reproduce and screenshots.
  • Phase-driven workflow (Plan, Explore, Collect Evidence, Categorize, Report) that can be tailored to testing scope and target URLs.

Quick Start

Provide a target URL and testing scope, then run the dogfood skill to start automated exploratory QA sessions.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory testing for web apps to uncover hidden bugs?

Exploratory testing for web apps is automated using a structured five-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. You simply provide a target URL and testing scope to navigate sites, capture screenshots, and generate structured bug reports.

What is the best way to generate a structured bug report with steps to reproduce?

The best way to generate a structured bug report is to use an exploratory QA workflow that categorizes observed issues and collects evidence. This approach automatically documents the steps to reproduce and captures screenshots during the testing session.

Can I capture screenshots as evidence during browser-based QA testing?

Yes, you can capture screenshots as evidence during browser-based QA testing. The workflow uses a browser toolset to interact with web elements and automatically collects visual evidence, which is then categorized and included in the final bug report.

How do I plan and define the scope for a web application QA session?

You plan and define the scope for a web application QA session by providing a target URL, testing scope, and output directory as inputs. The skill uses these inputs to drive the initial Plan phase, tailoring the exploratory testing to your specified boundaries.

Does exploratory QA testing work with sites that have varied testing scopes?

Yes, exploratory QA testing works with sites with varied scopes. The phase-driven workflow can be tailored to the specific testing scope and target URLs you provide, ensuring the exploration and evidence collection fit your requirements.