dogfood

Guide structured exploratory QA testing of web applications with evidence collection and reporting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Aevonix/colony-ai --skill dogfood-aevonix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Aevonix/colony-ai/tree/main/skills/dogfood
Command: npx skills add https://github.com/Aevonix/colony-ai --skill dogfood-aevonix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA of web applications often requires a repeatable, auditable process to locate bugs, collect evidence, and generate structured reports.

Core Features & Use Cases

  • Guided five-phase workflow: plan, explore, collect evidence, categorize issues, and report.
  • Evidence capture: screenshots, logs, and reproducible steps to support bug reports.
  • Template-driven reporting: standardized dogfood-style reports for consistent documentation.

Quick Start

Start a test session by loading a target URL and following the five-phase workflow to plan, explore, collect evidence, categorize issues, and generate a 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 exploratory QA testing of web applications?

Automate exploratory QA testing by following a structured five-phase workflow: plan, explore, collect evidence, categorize issues, and report. This process guides browser interactions to locate bugs and generate standardized documentation.

What is the best way to collect evidence for bug reports in web testing?

The best way to collect evidence for web testing bug reports is to capture screenshots, console logs, and reproducible steps during browser exploration. This creates screenshot-backed, auditable documentation that supports structured reports.

How do I generate standardized bug reports for complex UI interactions?

Generate standardized bug reports for complex UI interactions by using a template-driven reporting approach. This organizes collected evidence, reproducible steps, and categorized issues into a consistent, repeatable dogfood-style report format.

Do I need a browser toolset to validate web application interactions?

Yes, you need a browser toolset to validate web application interactions. The testing process requires browser capabilities like navigate, snapshot, click, type, vision, and console to identify bugs and capture evidence effectively.

Can I use structured QA workflows for manual testing scenarios across different domains?

Yes, you can use structured QA workflows for manual testing scenarios across different domains. The guided process applies to identifying bugs in complex UIs, validating interactions, and producing repeatable reports regardless of the application domain.

Why does exploratory web testing require a repeatable workflow?

Exploratory web testing requires a repeatable workflow to ensure auditable bug location, evidence collection, and report generation. A structured process prevents inconsistent documentation and supports standardized bug reporting.