How this skill is triggered — by the user, by Claude, or both
Slash command
/gsd-core:gsd-verify-work [phase number, e.g., '4'] [--ws <name>][phase number, e.g., '4'] [--ws <name>]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Purpose: Confirm what Claude built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase
<execution_context>
@/.claude/gsd-core/workflows/verify-work.md
@/.claude/gsd-core/templates/UAT.md
</execution_context>
Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.
npx claudepluginhub open-gsd/gsd-coreVerifies phase builds match plans with automated checks against must-haves and interactive UAT walkthroughs. For PBR workflows; supports --auto-fix, --teams, model overrides.
Verifies feature completion by requiring automated tests that prove functionality works. Enforces phase gates and spec alignment before acceptance.