bmad-validation-frontend

Execute Validation Metier items in a real browser and generate verdicts, screenshots, and network traces.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-validation-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validation-frontend
Source: https://github.com/florian-trehaut/bmad-global/tree/main/src/bmm-skills/4-implementation/bmad-validation-frontend
Command: npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-validation-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend validation workflows are heavy and error-prone without automated, observable proof from real user environments. This skill provides a structured method to execute VMs in a real browser, capture evidence, and decide pass/fail.

Core Features & Use Cases

  • Executes each Validation Metier item in a real browser to produce tangible proof and Verdicts.
  • Supports environment configuration, step activation, and proof standards integration.
  • Example use case: Validate a critical frontend flow across dev, staging, and production environments with real browser tests and a tracker-ready report.

Quick Start

Start a validation run by loading this skill and following the on-screen workflow prompts.

Frequently Asked Questions about bmad-validation-frontend

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

FAQPage Schema
How do I automate frontend validation with real browser tests?

Frontend validation is automated by executing each validation item in a real browser to generate verifiable verdicts, screenshots, and network traces. This structured workflow integrates proof standards and tracker-ready reporting for stakeholder reviews.

What is the best way to capture frontend test evidence across multiple environments?

Capturing frontend test evidence is handled by applying strict proof standards during real browser executions across dev, staging, and production. The workflow outputs verifiable pass/fail verdicts, screenshots, and network traces for review.

How do I generate tracker-ready reports for end-to-end browser testing?

Tracker-ready reports are generated by executing validation items in a real browser and capturing the resulting pass/fail verdicts alongside screenshots and network traces. This structured output is designed directly for stakeholder reviews.

Does this frontend validation workflow support environment setup and step activation?

Environment setup and step activation are supported within the frontend validation workflow. These features allow you to configure target environments and control the execution sequence of validation items during the real browser test runs.

Why use a real browser for frontend validation instead of simulated test environments?

A real browser is used for frontend validation to produce tangible proof and observable verdicts that simulated environments cannot guarantee. This method ensures verifiable results by capturing actual screenshots and network traces during execution.

Can I validate critical frontend flows across dev, staging, and production environments?

Validating critical frontend flows across dev, staging, and production environments is fully supported. The workflow executes validation items in a real browser across these configured environments to deliver tracker-ready reports with verifiable proof.