tad-test-brief

Generate and update TEST_BRIEF.md files for Claude Code + Playwright E2E pair testing using the 4D Protocol.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill tad-test-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tad-test-brief
Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/tad-test-brief
Command: npx skills add https://github.com/Sheldon-92/TAD --skill tad-test-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature streamlines the creation and maintenance of end-to-end pair testing briefs by automatically generating or updating TEST_BRIEF.md for paired testing with Claude Code + Playwright using the 4D Protocol, reducing manual drafting overhead.

Core Features & Use Cases

  • Generate or update a TEST_BRIEF.md for E2E pair testing with Claude Code + Playwright (4D Protocol).
  • Auto-fill sections from project context, recent changes, and previous sessions to provide a complete, ready-to-run brief.
  • Template-driven output with design intent, scope, test data, known issues, and technical notes to guide testing.

Quick Start

Run the pair-testing script to generate or update the TEST_BRIEF.md for the current project.

Frequently Asked Questions about tad-test-brief

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

FAQPage Schema
How do I generate an E2E pair testing brief for Claude Code and Playwright?

To generate an E2E pair testing brief, this Skill automates the creation and updating of TEST_BRIEF.md for Claude Code and Playwright using the 4D Protocol. It automatically gathers project context and recent changes to produce a ready-to-run document.

What is the 4D Protocol for E2E testing sessions?

The 4D Protocol is a structured pair testing framework used with Claude Code and Playwright. It ensures consistent documentation across sessions and test runs by standardizing design intent, scope, test data, and technical notes in the output brief.

Can I auto-fill test data and design intent in a TEST_BRIEF.md file?

Yes, you can auto-fill test data and design intent in a TEST_BRIEF.md file. The Skill uses a template-driven approach to extract information from project context, recent changes, and previous sessions to populate these specific sections automatically.

Does this pair testing brief generator work without external dependencies?

Yes, the pair testing brief generator works without external dependencies. It operates independently to apply the 4D Protocol, gathering automated context and managing sessions to generate the required testing documentation.

How do I update an existing test brief across multiple pair testing sessions?

To update an existing test brief across multiple sessions, the Skill reads previous session data and recent project changes. It then updates the TEST_BRIEF.md file to maintain consistent documentation for ongoing E2E pair testing.