dogfood

Guide exploratory web QA testing and generate categorized bug reports.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill dogfood-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/devMoez/titan/tree/main/skills/dogfood
Command: npx skills add https://github.com/devMoez/titan --skill dogfood-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you reliably find functional, visual, accessibility, UX, content, and console issues in a web application by enforcing a structured exploratory testing workflow with captured evidence.

Core Features & Use Cases

  • Five-phase exploratory QA workflow: plan, explore, collect evidence, categorize issues, and generate a report.
  • Browser-tool-driven evidence capture: navigation, DOM snapshots, console checks, annotated element screenshots, and post-interaction verification.
  • Issue classification with severity + taxonomy: organizes findings using a consistent severity (Critical/High/Medium/Low) and category framework, producing a de-duplicated, sorted set of issues.
  • Use case: testing a production marketing site or authenticated web app flow (login, search, forms, checkout) to produce an actionable, evidence-backed bug report package.

Quick Start

Run dogfood on https://example.com with scope set to full site, and save results to ./dogfood-output by following the workflow phases.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I systematically perform exploratory testing on web applications with evidence?

Exploratory testing for web applications follows a five-phase workflow: plan, explore, collect evidence, categorize issues, and generate a report. It systematically captures browser-based evidence like DOM snapshots and annotated screenshots to verify user flows and edge cases.

What's the best way to triage and classify bugs found during browser testing?

Bug reporting during browser testing uses a severity-category taxonomy to classify issues. Findings are organized by severity levels—Critical, High, Medium, or Low—and sorted into a de-duplicated set to produce an actionable markdown report.

How do I capture console output and DOM snapshots when testing web app user flows?

Browser toolsets capture console output and DOM snapshots by navigating planned pages, interacting with forms, and inspecting web app user flows. This evidence collection verifies post-interaction states and identifies functional or visual issues.

Can I use this structured QA workflow for production sites and authenticated web app flows?

Structured QA workflows apply to production marketing sites and authenticated web app flows. It tests login, search, forms, and checkout processes by executing responsive and visual checks to produce an evidence-backed bug report package.

Do I need a specific browser toolset to automate evidence screenshots for issue triage?

A browser toolset is required to automate issue triage. It navigates web pages, captures annotated and non-annotated screenshots, inspects console output, and verifies post-interaction states to generate a final markdown report from a template.