e2e-test-design

Design end-to-end test suites with golden-path and adversarial cases.

7|4|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/nklisch/skills --skill e2e-test-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test-design
Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/e2e-test-design
Command: npx skills add https://github.com/nklisch/skills --skill e2e-test-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing is often neglected or written without a full understanding of real user journeys and failure modes, leaving integration bugs to reach production. This Skill closes that gap by guiding a thorough, repository-aware design process that produces repeatable, user-focused e2e test suites.

Core Features & Use Cases

  • Repository exploration: Systematically find entry points, config, CI, and existing test infrastructure to ground test design in the real codebase.
  • User-journey mapping: Produce golden-path tests that represent complete user workflows and adversarial tests that verify graceful failure handling.
  • Interactive checkpoints: Ask targeted questions about failure expectations and target users to align assertions with project philosophy.
  • Use Case: When adopting a legacy CLI or web service, use this Skill to document core journeys, identify gaps in integration coverage, and produce a prioritized e2e test plan for CI integration.

Quick Start

Design an end-to-end test suite by exploring the repository, summarizing user journeys, asking about expected failures, and writing a structured Markdown test design document into the project.

Frequently Asked Questions about e2e-test-design

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

FAQPage Schema
How do I design an end-to-end test suite for a monorepo or CLI tool?

You can design end-to-end test suites for CLI tools, web apps, API servers, and monorepos by exploring the repository to find entry points, mapping user journeys, and generating a structured Markdown test plan compatible with existing CI infrastructure.

What is the best way to plan integration tests that cover failure modes?

Plan integration tests covering failure modes by using interactive checkpoints to define expected errors, then generating adversarial test cases alongside golden-path tests. This ensures the test suite verifies both normal user workflows and graceful failure handling.

How do I create e2e tests that fit into my existing CI pipeline and test directories?

Create e2e tests that fit existing CI pipelines by exploring your current test infrastructure and configuration, then outputting a structured Markdown test design document. This document aligns with your project's existing test directories and validation workflows.

Does this e2e test design approach work for legacy codebases without existing integration tests?

Yes, this e2e test design approach works for legacy codebases by systematically exploring repository architecture to document core user journeys. It identifies gaps in integration coverage and produces a prioritized test plan for CI integration.

How do I map golden-path user journeys for a web application or API server?

Map golden-path user journeys for web apps and API servers by analyzing repository code and documentation to identify complete user workflows. The process translates these workflows into structured test cases that represent full user-facing behavior.