plugins/gsd/skills/verify-work/SKILL.md
Validate built features through conversational UAT
npx skillsauth add davepoon/buildwithclaude gsd:verify-workInstall 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.
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 </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/verify-work.md @${CLAUDE_PLUGIN_ROOT}/templates/UAT.md </execution_context>
<context> Phase: $ARGUMENTS (optional) - If provided: Test specific phase (e.g., "4") - If not provided: Check for active sessions or prompt for phaseContext files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.
</context>
<output_format>
When this workflow concludes (verification passed or routed to gap closure), emit a Next Up continuation block following the pattern in references/continuation-format.md:
## ✓ Verification Passed or ## ⚠ Gaps Found — Routing to Plan with details)## ▶ Next Up heading with the next likely command (/gsd:complete-milestone if all phases verified, /gsd:plan-phase --gaps if gaps found, /gsd:next if unsure)`/clear` then: before the command/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)Verification accumulates lots of test/UAT prose that won't help downstream; phase-end is a clean boundary for /clear.
</output_format>
tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
data-ai
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
tools
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
development
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.