gsd-add-tests

Generate unit and E2E tests from phase specifications and UAT criteria.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-add-tests-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-add-tests
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-add-tests-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the manual effort of writing and validating tests after a development phase is completed, ensuring coverage matches UAT criteria and the phase documentation.

Core Features & Use Cases

  • Phase-based test generation: Uses SUMMARY.md, CONTEXT.md, and VERIFICATION.md as the single source of truth for what to test.
  • Implementation-aware classification: Scans implementation files and categorizes coverage as TDD (unit), E2E (browser), or Skip.
  • Approval-gated workflow: Produces a test plan for user approval and then generates tests following RED-GREEN conventions, preserving workflow gates and gap reporting.

Quick Start

Use the gsd-add-tests command with the target phase to generate and commit unit and E2E tests that satisfy the phase’s UAT criteria.

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 E2E tests from completed development phase documentation?

You generate unit and E2E tests by scanning implementation files against SUMMARY.md, CONTEXT.md, and VERIFICATION.md to map coverage to UAT criteria and produce an approval-gated test plan.

What is RED-GREEN verification in test generation?

RED-GREEN verification is a test generation convention where tests are produced and validated against phase specifications, ensuring test plans pass approval gates before achieving passing status.

Does this test generation workflow support categorizing implementation files as unit tests or E2E tests?

Yes, the test generation workflow scans implementation files and classifies coverage into TDD unit tests, E2E browser tests, or Skip categories, requiring classification approval before executing the plan.

Can I use GitHub Actions to run automated test plans generated from UAT criteria?

You can use GitHub Actions to run automated test plans generated from UAT criteria, executing the end-to-end add-tests workflow while preserving classification approval and gap reporting.

What's the best way to ensure test coverage matches UAT criteria after a development phase?

The best way to ensure test coverage matches UAT criteria is to use phase documentation as the single source of truth, scanning implementation files to produce an approval-gated test plan with gap reporting.

Why does my generated test plan require approval before writing tests?

Your generated test plan requires approval because the workflow preserves an approval-gated process, ensuring user validation of the implementation-aware classification before proceeding to RED-GREEN test generation.