e2e-specify

Generate test-analysis.md and e2e-test.md from specifications using MFQ&PPDCS and TCON.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill e2e-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-specify
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/e2e-specify
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill e2e-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables teams to automatically perform end-to-end test analysis and design directly from product or system specifications, eliminating manual interpretation and accelerating QA workflows.

Core Features & Use Cases

  • MFQ&PPDCS-based analysis to derive test points from requirements
  • TCON-based black-box test case design with Given-When-Then scenarios
  • Automatic generation of test-analysis.md and e2e-test.md artifacts for traceability

Quick Start

Provide a complete test analysis and a set of black-box test cases from the current specification.

Frequently Asked Questions about e2e-specify

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

FAQPage Schema
How do I automate end-to-end test analysis from product specifications?

You can automate end-to-end test analysis by feeding initial specifications into a tool that applies MFQ&PPDCS to derive test points and TCON to design black-box test cases, generating actionable test-analysis.md and e2e-test.md artifacts automatically.

What is MFQ&PPDCS methodology for test point derivation?

MFQ&PPDCS is an analysis methodology used to systematically derive test points from product requirements. It processes initial specifications and clarifications to extract requirements and map them into structured test points for comprehensive end-to-end coverage.

How to generate Given-When-Then black-box test cases from requirements?

To generate Given-When-Then black-box test cases, apply the TCON design approach to your extracted test points. This produces structured e2e-test.md artifacts containing actionable scenarios with full traceability mapping back to the original specifications.

Can I get traceability mapping between generated test cases and initial specifications?

Yes, traceability mapping is generated automatically. The workflow extracts requirements from initial specifications and clarifications, derives test points, and maps the final black-box test cases directly back to those original requirements in the output artifacts.

Does automated test design work for complex system specifications and clarifications?

Automated test design works for complex system specifications by parsing the initial documents and clarifications together. It extracts requirements, applies MFQ&PPDCS for analysis, and generates comprehensive test artifacts without manual interpretation.

What is the best way to eliminate manual interpretation in QA test workflows?

The best way to eliminate manual interpretation in QA workflows is to automate end-to-end test analysis and design directly from specifications. This accelerates QA processes by automatically producing test-analysis.md and e2e-test.md artifacts with traceability.