skills/add-tests/SKILL.md
Generate tests for a completed phase based on UAT criteria and implementation
npx skillsauth add jnuyens/gsd-plugin gsd:add-testsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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_PLUGIN_ROOT}/workflows/add-tests.md </execution_context>
<context> Phase: $ARGUMENTS@.planning/STATE.md @.planning/ROADMAP.md </context>
<process> Execute the add-tests workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/add-tests.md end-to-end. Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting). </process>testing
Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.
tools
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
tools
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
testing
Extract decisions, lessons, patterns, and surprises from completed phase artifacts