dogfood

Automate exploratory QA testing of web applications with a browser toolset.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jacardl/New-Radar --skill dogfood-jacardl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/jacardl/New-Radar/tree/main/backend/frameworks/hermes-agent/skills/dogfood
Command: npx skills add https://github.com/jacardl/New-Radar --skill dogfood-jacardl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, phase-driven approach to uncover defects in web applications by guiding automated and manual QA testers through planning, exploration, evidence collection, categorization, and reporting.

Core Features & Use Cases

  • Phase-driven QA workflow across Plan, Explore, Collect Evidence, Categorize, and Report.
  • Built-in browser toolset guidance for navigating pages, capturing screenshots, inspecting DOM, and logging console output.
  • Produce a structured bug report with evidence paths and a summary suitable for stakeholders.
  • Use cases include manual QA exploration of enterprise web apps, regression testing, and cross-page compatibility checks.

Quick Start

Provide a target URL and testing scope to start a five-phase QA run using the built-in browser tools.

Frequently Asked Questions about dogfood

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

FAQPage Schema
What is exploratory QA testing for web apps and how does it work?

Exploratory QA testing for web apps is a structured approach to uncover defects by navigating target URLs and capturing evidence. It works through a phase-driven workflow covering planning, exploration, evidence collection, categorization, and reporting.

How do I automate bug reporting and evidence capture during web app testing?

Automate bug reporting and evidence capture by using a browser toolset to inspect DOM, log console output, and capture screenshots. The workflow collects these artifacts during exploration and compiles them into a structured bug report.

What do I need to start manual QA exploration of a web application?

To start manual QA exploration of a web application, you need to provide a target URL and define a testing scope. This input initiates a five-phase QA run using built-in browser tools to guide the process.

Can I use this exploratory testing approach for regression testing and cross-page compatibility checks?

Yes, you can use this exploratory testing approach for regression testing and cross-page compatibility checks. The phase-driven workflow supports navigating multiple pages, capturing defects, and generating a summary suitable for stakeholders.

What is the best way to structure a bug report with evidence artifacts for stakeholders?

The best way to structure a bug report with evidence artifacts is to follow a categorize and report phase. This process organizes collected screenshots and console logs into a structured summary with evidence paths suitable for stakeholders.

Does exploratory QA testing work without predefined test scripts?

Yes, exploratory QA testing works without predefined test scripts by applying a phase-driven workflow to guide testers. It focuses on planning, exploring, and gathering evidence across target URLs and defined scopes rather than executing scripted steps.