10-e2e

Verifies user journeys across web, API, and CLI projects via adaptive parallel execution.

1|Updated May 31, 2026
One-click install
npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 10-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10-e2e
Source: https://github.com/joseph-c-mcguire/spec-driven/tree/main/.cursor/skills/10-e2e
Command: npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 10-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that user journeys from product requirements work seamlessly across various project types, providing a comprehensive verification mechanism.

Core Features & Use Cases

  • Adaptive Mechanism: Automatically selects the appropriate verification method based on the project type (browser automation, API calls, shell execution, library import).
  • Parallel Execution: Runs verification tasks in parallel, enhancing efficiency.
  • Integration with QA: Works alongside QA stages to ensure a comprehensive testing process.
  • Use Case: For a web application, it automatically verifies end-to-end user journeys by simulating user interactions in a browser environment.

Quick Start

Use the 10-e2e skill to verify the end-to-end user journey for your web application.

Frequently Asked Questions about 10-e2e

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

FAQPage Schema
How do I verify end-to-end user journeys across different project types?

End-to-end user journey verification is achieved using adaptive mechanisms that automatically select browser automation, API calls, shell execution, or library import based on your specific project configuration.

Can I run end-to-end testing tasks in parallel for my web application?

Yes, parallel execution runs verification tasks simultaneously across various project types. This enhances testing efficiency when verifying user journeys from your product requirements documentation.

Does end-to-end testing work for both web applications and CLI tools?

End-to-end testing adapts to multiple project types including web applications, APIs, and CLI tools. It automatically selects the appropriate verification method, such as shell execution for CLI tools.

What do I need to provide to verify user journeys from product requirements?

Verifying user journeys requires your product requirements documentation and project-specific configurations. The adaptive mechanism uses these inputs to determine the correct testing approach.

How does adaptive verification choose between browser automation and API calls?

Adaptive verification selects the appropriate method by analyzing your project type and configurations. It automatically determines whether to execute browser automation, API calls, shell execution, or library imports.

When should I integrate end-to-end verification into my QA process?

Integrate end-to-end verification alongside your existing QA stages to ensure a comprehensive testing process. It works alongside QA stages to confirm user journeys work seamlessly across project types.