skills.rest
WeWake1
WeWake1COMMUNITY
Explore all skills by this author →
GitHub

gsd-add-tests

Generates unit and E2E tests for a completed phase from UAT criteria and implementation files.

Updated Mar 15, 2026
Search Tags:#unit tests#tdd#test generation#e2e tests#test plan#red-green#phase workflow
One-click install
npx skills add https://github.com/WeWake1/BSOMS --skill gsd-add-tests-wewake1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/WeWake1/BSOMS/tree/main/.agent/skills/gsd-add-tests
Command: npx skills add https://github.com/WeWake1/BSOMS --skill gsd-add-tests-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a development phase, teams often skip or delay writing tests because it requires manually reviewing implementation files and deciding what to test. This Skill automates that gap by turning phase documentation into a concrete, approved test suite. ## Core Features & Use Cases - Implementation Classification: Analyzes phase files and classifies them into TDD (unit), E2E (browser), or Skip categories before writing any test. - Approval-Gated Workflow: Presents a test plan for user approval and enforces RED-GREEN verification conventions with gap reporting. - Use Case: After completing phase 3 of a roadmap, run the Skill with the phase number to generate unit and E2E tests derived from SUMMARY.md, CONTEXT.md, and VERIFICATION.md, committed as test(phase-3): add unit and E2E tests from add-tests command. ## Quick Start Ask the assistant to run the add-tests workflow for phase 3 to generate and commit unit and E2E tests from that phase's documentation.

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 tests for a completed development phase?▼

Run the add-tests workflow with the phase number as the argument. The Skill reads the phase's SUMMARY.md, CONTEXT.md, and VERIFICATION.md, classifies implementation files, presents a test plan for approval, then generates unit and E2E tests.

How does the Skill decide between unit tests and E2E tests?▼

It analyzes the implementation files and classifies each into TDD (unit), E2E (browser), or Skip categories. This classification is presented to you for approval before any test code is written.

What inputs does the add-tests workflow require?▼

It requires a phase number argument plus the phase documentation files SUMMARY.md, CONTEXT.md, and VERIFICATION.md, along with project state files STATE.md and ROADMAP.md for context.

Does the Skill commit the generated tests automatically?▼

Yes, generated test files are committed with the message format `test(phase-{N}): add unit and E2E tests from add-tests command`, where N is the phase number you provided.

What happens if some files cannot be tested?▼

Files that do not fit unit or E2E testing are placed in the Skip category during classification. The workflow also includes gap reporting so untested areas are surfaced rather than silently ignored.

Related Skills

Explore More Software Engineering Skills→
thecomputer07thecomputer07

qsd-add-tests

Generate unit and E2E tests from phase specifications and commit them.

Community
Intermediate
awfixers-stuffawfixers-stuff

e2e

Classify Playwright and Vitest end-to-end test failures as flaky, outdated, bug, or unverified.

Official
Advanced
Pear-CommercePear-Commerce

gsd-add-tests

Generate unit and end-to-end tests from UAT criteria and phase documents.

Official
Intermediate
791994545791994545
4

tdd

Guide developers through the RED-GREEN-REFACTOR Test-Driven Development cycle.

Community
Intermediate