validate

Execute acceptance scenarios and capture screenshot evidence across platforms.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/bernajaber/pi-product-system --skill validate-bernajaber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/validate
Command: npx skills add https://github.com/bernajaber/pi-product-system --skill validate-bernajaber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates manual, inconsistent verification of product acceptance scenarios by walking through every scenario, performing platform-appropriate interactions, and collecting reproducible visual evidence to support Gate 3 decisions.

Core Features & Use Cases

  • Multi-strategy validation for web, dev-server (Electron/Tauri), native macOS, Flutter desktop, and CLI workflows with heuristics to choose the right approach.
  • Automated evidence collection using agent-browser (Playwright) for web, screencapture and cliclick for native apps, and test output reporting for CLI tools.
  • Gate 3 presentation & feedback loop: compiles scenario PASS/FAIL, screenshots, and a Portuguese checklist, and integrates with the code quality loop and scout subagent for automatic diagnosis and re-entry to build cycles.
  • Use Case: verify a feature built by the product system by executing every acceptance scenario, capturing at least one result screenshot per scenario, and presenting the operator with a consolidated Gate 3 checklist.

Quick Start

Run the validate skill to walk every acceptance scenario, capture screenshots as evidence, and present Gate 3 to the operator in Portuguese.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I automate acceptance testing with screenshot evidence for web and native macOS apps?

Acceptance testing with screenshot evidence is generated by walking through every scenario using Playwright for web or screencapture and cliclick for native macOS, then recording PASS/FAIL outcomes with screenshot file paths.

Does Playwright work for Flutter desktop and Electron dev-server acceptance validation?

Playwright supports web and dev-server validation for Electron and Tauri, while Flutter desktop and native macOS use platform-specific heuristics with screencapture and cliclick to capture visual evidence.

What is the best way to verify built product acceptance scenarios across multiple platforms?

Verifying built product acceptance scenarios across web, dev-server, native macOS, Flutter desktop, and CLI is handled by reading the feature plan to choose a strategy, executing responsive checks, and compiling a Gate 3 checklist.

How do I execute responsive and platform-specific checks for CLI tools?

Responsive and platform-specific checks for CLI tools are executed using test output reporting to validate scenarios, rather than capturing screenshots, ensuring command-line workflows meet acceptance criteria.

Why does acceptance scenario validation require passing tests and code review?

Acceptance scenario validation requires passing tests and code review to ensure the built product meets quality standards before executing scenarios, capturing screenshots, and presenting Gate 3 feedback for diagnosis and build re-entry.