e2e-validate

Orchestrate end-to-end validation pipelines with platform detection, journey mapping, and evidence capture.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/krzemienski/validationforge --skill e2e-validate-krzemienski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-validate
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/e2e-validate/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill e2e-validate-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects the correct platform and orchestrates a full end-to-end validation pipeline that maps user journeys, defines PASS criteria, captures and reads verifiable evidence, and produces auditable verdicts without using mocks or test doubles.

Core Features & Use Cases

  • Platform Detection: Auto-detect iOS, React Native, Flutter, web, API, CLI, Django, fullstack or generic projects to select the appropriate validation strategy.
  • Journey Mapping & Planning: Inventory entry points, prioritize journeys (P0–P3), and generate measurable PASS criteria before execution.
  • Execution & Evidence: Build/start the real system, exercise journeys bottom-up, capture screenshots/logs/responses to e2e-evidence/, READ evidence, and match it to criteria.
  • Fix Loop & CI Mode: Support a 3-strike fix-and-revalidate protocol and non-interactive CI runs that emit structured logs and exit codes.
  • Use Case: Run in CI to block merges when critical journeys fail or run interactively to audit production readiness with cited evidence.

Quick Start

Run the e2e-validate pipeline to detect the platform, generate a validation plan, execute journeys, capture and read evidence, and save the final e2e-evidence/report.md.

Frequently Asked Questions about e2e-validate

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

FAQPage Schema
How do I run end-to-end validation without using mocks or test doubles?

End-to-end validation without mocks orchestrates real-system interactions by building the system, executing user journeys, capturing screenshots and logs, and matching evidence to PASS criteria. It produces auditable verdicts without test doubles.

Can I automate end-to-end testing in CI and block merges when critical journeys fail?

Yes, you can automate end-to-end testing in CI using non-interactive runs that emit structured logs and exit codes. This allows pipelines to block merges when critical P0–P3 user journeys fail validation.

Does the validation pipeline support iOS, React Native, Flutter, and Django projects?

Yes, the validation pipeline auto-detects iOS, React Native, Flutter, web, API, CLI, Django, and fullstack projects. It selects the appropriate validation strategy based on the detected platform.

What is the 3-strike fix protocol for failed end-to-end validation?

The 3-strike fix protocol is an automated fix-and-revalidate loop for failed end-to-end validation. It attempts to resolve failures up to three times, re-executing journeys and re-checking evidence before producing a final verdict.

How do I capture and read evidence during an end-to-end validation run?

To capture and read evidence, the validation pipeline exercises user journeys and saves screenshots, logs, and responses to an e2e-evidence directory. It then reads these artifacts and matches them against generated PASS criteria.