e2e-test-design

Design end-to-end test suites by analyzing codebases and failure scenarios.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/KevounC/claude-kanban --skill e2e-test-design-kevounc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test-design
Source: https://github.com/KevounC/claude-kanban/tree/main/.claude/skills/e2e-test-design
Command: npx skills add https://github.com/KevounC/claude-kanban --skill e2e-test-design-kevounc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the design of a comprehensive end-to-end test suite for a project, saving time and ensuring comprehensive coverage.

Core Features & Use Cases

  • Comprehensive Test Suite Design: Designs both golden-path and adversarial/failure-mode tests.
  • Interactive Workflow: Guides through understanding the codebase, intended usage, and failure expectations.
  • Documentation Generation: Outputs a detailed test design document to the project.

Quick Start

Use the e2e-test-design skill to create a test suite for your 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 an existing codebase?

To design an end-to-end test suite, this Skill analyzes your codebase and project documentation to understand intended usage, then generates detailed test design documentation covering both user-facing behavior and integration testing.

What is included in automated end-to-end test design?

Automated end-to-end test design includes analyzing your codebase to generate comprehensive test suites, focusing on both golden-path workflows and adversarial failure-mode scenarios to ensure thorough coverage.

Do I need project documentation to generate end-to-end tests?

Yes, you need project documentation and codebase access. The interactive workflow relies on analyzing code and understanding intended usage along with failure expectations to output accurate test design documents.

What's the best way to automate failure scenario testing for software projects?

The best way to automate failure scenario testing is using an interactive workflow that analyzes your codebase to understand expected failures and generates adversarial test cases alongside golden-path tests.

Can I use code analysis to generate integration testing documentation?

Yes, code analysis can generate integration testing documentation. By analyzing the codebase and understanding user-facing behavior, the Skill outputs a detailed test design document focusing on integration points.