dev-webtest-plan

Generate and update Playwright end-to-end test plans from development specifications.

Updated May 5, 2026

Search Tags:#test automation #acceptance criteria #playwright #e2e testing #dev-plan #test plan generation #screen specifications

Ready to run

npx skills add https://github.com/seiei-sogen/tumigi --skill dev-webtest-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-webtest-plan
Source: https://github.com/seiei-sogen/tumigi/tree/main/skills/dev-webtest-plan
Command: npx skills add https://github.com/seiei-sogen/tumigi --skill dev-webtest-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the manual effort of creating and maintaining Playwright end-to-end test plans by automatically generating them from development plans and acceptance criteria, or by updating existing plans when screen specifications change.

Core Features & Use Cases

New Plan Generation: Creates comprehensive Playwright test plans from dev-plan outputs including acceptance criteria, task test strategies, and implementation code analysis.
Differential Updates: Updates existing test plans based on screen specification changes, tracking additions, modifications, and deletions.
Dual Mode Operation: Supports Full-spec mode with acceptance criteria and Lightweight mode without them for flexible workflow integration.

Quick Start

Use the dev-webtest-plan skill to generate a Playwright test plan from your existing dev-plan named "user-authentication".

Frequently Asked Questions about dev-webtest-plan

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

FAQPage Schema

How do I auto-generate Playwright E2E test plans from screen specifications?▼

Playwright E2E test plans are auto-generated by converting development specifications and acceptance criteria into executable web test scenarios. The skill analyzes task test strategies and implementation code to produce traceable test plans with API setup and cleanup procedures.

Can I generate Playwright test plans without acceptance criteria?▼

Playwright test plans can be generated without acceptance criteria using lightweight mode. This mode provides flexible workflow integration by deriving test scenarios from task test strategies and implementation code analysis, while full-spec mode utilizes the complete acceptance criteria.

How do I update existing Playwright E2E tests when screen specifications change?▼

Existing Playwright E2E tests are updated through differential updates that track additions, modifications, and deletions in screen specifications. This approach modifies the current test plans based on the identified changes instead of regenerating the entire test suite.

What is the best way to trace confidence levels in generated Playwright test scenarios?▼

Playwright test scenarios are traced using signal indicators for confidence levels embedded within the generated test plan. These indicators provide visibility into the reliability of the automated test scenarios derived from the development specifications.

Do I need API setup and cleanup procedures in my Playwright E2E test plan generation?▼

API setup and cleanup procedures are automatically included when generating Playwright E2E test plans. The skill integrates these procedures into the executable web test scenarios to ensure proper test environment initialization and teardown.

When should I use full-spec mode over lightweight mode for Playwright test plan generation?▼

Full-spec mode should be used when complete acceptance criteria are available to generate comprehensive Playwright test plans. Lightweight mode applies when acceptance criteria are absent, relying on task test strategies and implementation code analysis for flexible workflow integration.