dogfood

Automate exploratory QA testing of web applications with evidence-based bug reports.

97|8|Updated Mar 20, 2026

Search Tags:#testing #qa #evidence #browser #web #bug-report #dogfood

Ready to run

npx skills add https://github.com/peteromallet/megaplan --skill dogfood-peteromallet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/peteromallet/megaplan/tree/main/megaplan/agent/skills/dogfood
Command: npx skills add https://github.com/peteromallet/megaplan --skill dogfood-peteromallet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides systematic exploratory QA testing of web applications to identify bugs, capture evidence, and generate structured reports for stakeholders.

Core Features & Use Cases

Systematic exploratory testing across the browser toolset to uncover defects and inconsistencies.
Evidence capture and structured bug reporting aligned to the provided templates.
Reusable reporting workflow that yields a dogfood QA report suitable for audits and product feedback.

Quick Start

Run a dogfood QA session on a target web app, using the browser tools to explore pages, collect evidence, and generate the final report.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate systematic exploratory QA testing for web applications?▼

Systematic exploratory QA testing automates browser interactions to uncover web application defects and inconsistencies. This Skill guides the process across a browser toolset, capturing evidence and generating structured bug reports for stakeholder review.

What is the best way to generate evidence-based bug reports during manual QA workflows?▼

Evidence-based bug reports are generated by capturing browser interactions during exploratory testing and classifying findings using an issue taxonomy. This Skill applies structured templates to produce a final dogfood QA report suitable for audits and product feedback.

Do I need a specific browser toolset to run structured web QA testing?▼

Yes, running structured web QA testing requires a browser toolset capable of navigating, clicking, typing, and capturing evidence. You also need the dogfood-report-template and an issue taxonomy to classify findings and generate the final report.

Can I use this approach to collect evidence for audits and product feedback?▼

Yes, you can collect evidence for audits and product feedback by running exploratory QA sessions. This Skill yields a reusable dogfood QA report that aligns with structured templates, documenting defects and inconsistencies found during browser interactions.

How does systematic exploratory testing classify and structure web application bugs?▼

Systematic exploratory testing classifies web application bugs by applying a predefined issue taxonomy to the findings. It structures the captured evidence into a dogfood-report-template, producing a standardized report for stakeholders.

When should I not use exploratory QA testing for web application defects?▼

Exploratory QA testing is not suited for environments lacking a compatible browser toolset for navigation and evidence capture. It also requires an issue taxonomy and reporting template, making it less ideal for ad-hoc checks without structured reporting needs.