e2e

Coordinate end-to-end testing workflows with rule-based guidance for test-first development.

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/teslasoft-de/claude-skills-marketplace --skill e2e-teslasoft-de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/teslasoft-de/claude-skills-marketplace/tree/main/plugins/e2e/skills/e2e
Command: npx skills add https://github.com/teslasoft-de/claude-skills-marketplace --skill e2e-teslasoft-de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end testing workflows with rule-based guidance for test-first development.

Core Features & Use Cases

  • Rule 1: Test-First Development workflow
  • Rule 2: Progressive Testing for test modifications
  • Rule 3: Iterative Testing for refactoring
  • TodoWrite integration and dashboard results API
  • Context loading and triggers for /e2e and related commands

Quick Start

Invoke an E2E workflow by sending '/e2e' and pick a mode such as '/e2e new-feature' to start test-first development.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I coordinate end-to-end testing workflows for test-first development?

End-to-end testing workflows for test-first development are coordinated using rule-based guidance triggered by the /e2e command. It applies progressive rules across new features, test changes, and refactoring scenarios to manage the entire testing lifecycle.

How do I start a test-first workflow for a new feature?

To start a test-first workflow, invoke the /e2e command and select the 'new-feature' mode. This triggers Rule 1, guiding you through writing tests prior to implementation while tracking progress with TodoWrite integration.

Does this E2E testing workflow require a specific testing framework?

No, this E2E testing workflow does not require a specific testing framework. It provides framework-agnostic commands to guide test-first development, progressive testing, and iterative testing across any technology stack.

How do I track E2E testing progress and retrieve dashboard results?

E2E testing progress is tracked using TodoWrite integration, and dashboard results are retrieved via a dedicated API endpoint like GET /api/health/e2e. This provides visibility into the rule-based testing workflow status and outcomes.

What is the best way to handle E2E testing during code refactoring?

The best way to handle E2E testing during code refactoring is using the iterative testing rule. This mode modifies tests progressively, ensuring existing functionality remains intact throughout the refactoring workflow.