From GSD Core
Generates unit and E2E tests for a completed phase by analyzing implementation files against UAT criteria, presenting a test plan for approval, and committing RED-GREEN tests.
How this command is triggered — by the user, by Claude, or both
Slash command
/gsd-core:add-tests <phase> [additional instructions]gsd/Files this command reads when invoked
This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<objective>
Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command`
</objective>
<execution_context>
@~/.claude/gsd-core/workflows/add-tests.md
</execution_context>
<context>
Phase: $ARGUMENTS
@.planning/STATE.md
@.planning/...Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message test(phase-{N}): add unit and E2E tests from add-tests command
<execution_context> @~/.claude/gsd-core/workflows/add-tests.md </execution_context>
Phase: $ARGUMENTS@.planning/STATE.md @.planning/ROADMAP.md
Execute end-to-end. Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting).npx claudepluginhub seanb4t/gsd-core29plugins reuse this command
First indexed Jun 7, 2026
Showing the 6 earliest of 29 plugins
/add-testsGenerates unit and E2E tests for a completed phase by analyzing implementation files against UAT criteria, presenting a test plan for approval, and committing RED-GREEN tests.
/testGenerates tests for completed code phases by auto-detecting the test framework and targeting key files.
/add-testsGenerates and adds test coverage for a specific plan or phase after execution, following a defined workflow with gates and validations.
/testWrites and runs unit, integration, or E2E tests for provided code, acceptance criteria, and critical flows. Ensures coverage of happy paths, errors, edge cases; documents gaps.
/fire-verify-uatGuides conversational User Acceptance Testing by walking through critical flows and spawning parallel diagnostic agents on failures.
/test-planCreates a structured test plan from feature artifacts — queries test types, environment, and credentials, auto-detects the test framework, generates test cases mapped to user stories, and saves them under features/<name>/testing/.