gsd-add-tests

Generate unit and end-to-end tests from phase documentation.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-add-tests-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-add-tests
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-add-tests-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of turning a completed phase’s specifications into a concrete test suite, helping teams validate implementation against defined acceptance criteria.

Core Features & Use Cases

  • Test Planning: Reviews phase documentation and classifies implementation files into unit, end-to-end, or skip categories.
  • Test Generation: Produces tests using red-green conventions so coverage aligns with the completed phase’s behavior.
  • Workflow Guardrails: Preserves approval gates and verification steps to keep the test-generation process controlled and traceable.

Quick Start

Use the gsd-add-tests skill to analyze phase 2 specifications and generate the matching unit and end-to-end tests.

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 specifications?

The Skill generates unit and end-to-end tests by analyzing phase summary, context, and verification documents to classify implementation files and produce ready-to-run test files that validate expected behavior.

What is red-green verification in phase-based testing workflows?

Red-green verification is a testing convention where generated tests initially fail (red) against defined acceptance criteria, then pass (green) once the phase implementation correctly aligns with the expected behavior.

How do I classify implementation files for unit versus end-to-end testing?

Classifying implementation files for unit versus end-to-end testing involves reviewing phase documentation to determine if behavior requires isolated validation or broader workflow integration, including skipping non-critical files.

Can I maintain approval gates during automated test generation?

Yes, automated test generation can maintain approval gates. The process preserves existing workflow guardrails and verification steps to keep test creation controlled, traceable, and aligned with phase-based engineering standards.

What phase documentation do I need to create a test suite?

Creating a test suite requires phase documentation including summary, context, and verification documents. These define the expected behavior and acceptance criteria needed to generate accurate unit and end-to-end tests.

Why use a phase-based workflow for test generation instead of writing tests manually?

Phase-based test generation removes the manual effort of translating specifications into tests, ensuring coverage aligns with completed phase behavior while preserving traceability and verification steps required by structured engineering processes.