GS

gsd-add-tests

Generate automated tests for completed software phases using UAT criteria.

Install

mkdir -p .claude/skills/gsd-add-tests-phorde && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14840" && unzip -o skill.zip -d .claude/skills/gsd-add-tests-phorde && rm skill.zip

Installs to .claude/skills/gsd-add-tests-phorde

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Generate tests for a completed phase based on UAT criteria and implementation
77 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Generate unit tests for a completed phase
  • Generate E2E tests for a completed phase
  • Classify implementation files into TDD, E2E, or Skip categories
  • Present a test plan for user approval
  • Generate tests following RED-GREEN conventions
  • Commit generated test files with a specific message

How it works

The skill analyzes implementation files and uses SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications to generate unit and E2E tests. It classifies files, presents a test plan for approval, and then generates tests.

Inputs & outputs

You give it
User text after $gsd-add-tests, representing the phase argument
You get back
Test files committed with message 'test(phase-{N}): add unit and E2E tests from add-tests command'

When to use gsd-add-tests

  • Generate feature tests
  • Verify UAT criteria
  • Create test code for implementation

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-add-tests.
  • Treat all user text after $gsd-add-tests as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<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> @C:/ExtratorLaudos/.codex/get-shit-done/workflows/add-tests.md </execution_context>

<context> Phase: {{GSD_ARGS}}

@.planning/STATE.md @.planning/ROADMAP.md </context>

<process> Execute the add-tests workflow from @C:/ExtratorLaudos/.codex/get-shit-done/workflows/add-tests.md end-to-end. Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting). </process>

When not to use it

  • When the phase is not yet completed
  • When UAT criteria and implementation details are unavailable

Limitations

  • Requires a completed phase
  • Relies on SUMMARY.md, CONTEXT.md, and VERIFICATION.md for specifications
  • Requires user approval for the test plan

How it compares

This workflow automates test generation and commitment based on specific GSD phase documentation, unlike manual test creation.

Compared to similar skills

gsd-add-tests side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-add-tests (this skill)03moNo flagsIntermediate
dev26moReviewAdvanced
overnight-development11moReviewIntermediate
nx-run-tasks16moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry