gsd-add-tests

Generate unit and end-to-end tests for a completed GSD phase.

4|Updated Apr 11, 2026

Search Tags:#unit tests #testing #tdd #verification #end-to-end #red-green #gated workflow

Ready to run

npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-add-tests-electroheadfx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-add-tests
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-add-tests-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a completed GSD phase into a concrete test suite by deriving unit and end-to-end coverage from the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md files.

Core Features & Use Cases

Test Planning: Classifies implementation files into TDD, E2E, or Skip categories and presents the plan for approval.
Red-Green Workflow: Generates tests in a controlled sequence with verification and gap reporting.
Workflow Safety: Preserves approval gates so tests are not written before the required user confirmation.
Use Case: A developer finishes a phase and asks this Skill to produce the missing unit and browser tests for that phase's deliverables.

Quick Start

Ask the skill to generate tests for phase 3 from the phase summary, context, and verification documents.

Frequently Asked Questions about gsd-add-tests

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

FAQPage Schema

How do I generate unit and end-to-end tests from phase documentation?▼

Generate unit and end-to-end tests by analyzing implementation files alongside phase SUMMARY.md, CONTEXT.md, and VERIFICATION.md documents to derive concrete test suites for completed deliverables.

What is a gated red-green workflow for test generation?▼

A gated red-green workflow classifies source files into TDD, E2E, or Skip categories, requires plan approval, and sequentially generates tests with verification checks and gap reporting before committing.

Can I write tests before the test plan is approved?▼

No, the test plan must be approved first. The workflow strictly preserves approval gates so unit and end-to-end tests are not written before the required user confirmation is received.

How do I classify source files for TDD and E2E testing?▼

Classify source files by analyzing implementation files and phase documentation to categorize deliverables into TDD, E2E, or Skip buckets, then present the test plan for approval.

What files are needed to generate tests for a completed GSD phase?▼

You need the phase SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, plus the implementation files. These documents provide the context to derive unit and end-to-end coverage.

How are verification gaps reported during test generation?▼

Verification gaps are reported during the controlled red-green sequence. The workflow performs verification checks and gap reporting before committing the generated test files to ensure coverage.