swe-tdd

Convert PRDs into E2E test specification documents with traceability maps.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/MmtBkn/swe --skill swe-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-tdd
Source: https://github.com/MmtBkn/swe/tree/main/swe-tdd
Command: npx skills add https://github.com/MmtBkn/swe --skill swe-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill transforms Product Requirements Documents (PRDs) into comprehensive, end-to-end (E2E) first test specification documents, ensuring thorough validation and early detection of ambiguities.

Core Features & Use Cases

  • PRD to Test Spec Conversion: Automatically generates detailed test plans, including persona coverage, feature matrices, user stories, and E2E test scenarios.
  • Ambiguity Detection: Surfaces missing requirements and design gaps by iterating against the PRD.
  • Use Case: You have a new feature PRD and need a robust test plan to guide QA and development. Use this Skill to generate a detailed test specification document that covers all user flows, edge cases, and error conditions.

Quick Start

Use the swe-tdd skill to create a test specification document from the PRD located at '/path/to/your/prd.md'.

Frequently Asked Questions about swe-tdd

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

FAQPage Schema
How do I generate E2E test specifications from a PRD?

You can generate E2E test specifications from a PRD by using an automation tool to derive a comprehensive test plan covering persona coverage, user stories, and traceability maps for automated testing frameworks.

What is the best way to find missing requirements in a product requirements document?

The best way to find missing requirements in a PRD is to iterate against it using an automated test specification generator, which surfaces ambiguities and design gaps by mapping all requirements to testable scenarios.

Can I create Playwright test plans directly from a PRD file?

Yes, you can create Playwright test plans from a PRD file by deriving an E2E-first test specification document that maps user flows and edge cases into testable scenarios supporting automated E2E testing frameworks.

How does PRD to test spec conversion handle user stories and feature areas?

PRD to test spec conversion handles user stories and feature areas by automatically breaking down the PRD into a detailed feature matrix and persona coverage, ensuring all requirements map to comprehensive test scenarios.

Do I need a structured PRD to generate automated E2E testing scenarios?

Yes, you need a structured PRD to generate automated E2E testing scenarios, as the conversion process iterates against the provided document to extract feature-area breakdowns, user stories, and traceability maps.

Why does my test specification lack traceability for edge cases?

Your test specification may lack traceability for edge cases if the PRD was not iterated against to surface ambiguities, a process necessary to ensure all requirements are mapped to comprehensive testable scenarios.