e2e

Trace user flows across components and execute bottom-up end-to-end verification.

4|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/baleen37/bstack --skill e2e-baleen37
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/baleen37/bstack/tree/main/plugins/me/skills/e2e
Command: npx skills add https://github.com/baleen37/bstack --skill e2e-baleen37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end verification ensures that changes spanning multiple components, services, or layers actually work in the full user flow, not just in isolation.

Core Features & Use Cases

  • Trace complete user flows across components to identify breakpoints and data handoffs.
  • Define explicit pass/fail criteria for each step in the flow and generate a cohesive verification report.
  • Apply to multi-service deployments, API-contract changes, and data-flow alterations where unit/integration tests are insufficient.

Quick Start

Run an end-to-end verification across the affected components and report the results.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I verify complete user flows across multiple services after deployment?

You can verify multi-service user flows by tracing data paths across components, defining explicit pass/fail criteria for each step, executing in dependency order bottom-up, and producing a cohesive execution report.

When do I need end-to-end testing instead of unit or integration tests?

End-to-end testing is necessary when changes span multiple components, services, or layers, such as multi-service deployments, API-contract changes, and data-flow alterations where unit and integration tests are insufficient to validate the full user flow.

How do I trace data handoffs and identify breakpoints across API contracts?

Trace complete user flows across components to identify breakpoints and data handoffs by defining pass/fail criteria for each step, executing validations in bottom-up dependency order, and generating a verification report.

Can I use this for multi-service deployments and data-flow alterations?

Yes, this approach is specifically applicable to multi-service deployments, API-contract changes, and data-flow alterations, validating that changes spanning multiple components actually work in the full user flow rather than in isolation.

What's the best way to define pass/fail criteria for end-to-end verification?

Define explicit pass/fail criteria for each step in the user flow, execute the verification in dependency order bottom-up, and generate a cohesive execution report to confirm the changes work end-to-end across all affected components.