How do I install the Gsdverify Work skill?

Run npx skillmds add thedixitjain/gsdverify-work in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Gsdverify Work skill do?

Validate built features through conversational UAT It is listed under Coding & Dev Tools on SkillMD.

Is Gsdverify Work safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsdverify Work?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsdverify Work free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsdverify Work?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsdverify Work by thedixitjain — Agent Skill

Name: Gsdverify Work
Rating: 4.5 (4 reviews)
Author: thedixitjain

File contents

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

Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.

Show verification status (e.g., ## ✓ Verification Passed or ## ⚠ Gaps Found — Routing to Plan with details)
Emit a ## ▶ 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)
Use `/clear` then: before the command
Include a parenthetical: (/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)
Add an "Also available:" section with 1-3 alternatives where relevant

Verification accumulates lots of test/UAT prose that won't help downstream; phase-end is a clean boundary for /clear.

Source: davepoon/buildwithclaude → plugins/gsd/skills/verify-work/SKILL.md

---name: gsdverify-workdescription: Validate built features through conversational UAT--- <objective> Validate built features through conversational testing with persistent state. 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 phase Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks. </context> <process> Execute the verify-work workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process> <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`: - Show verification status (e.g., `## ✓ Verification Passed` or `## ⚠ Gaps Found — Routing to Plan` with details) - Emit a `## ▶ 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) - Use **`` `/clear` then: ``** before the command - Include a parenthetical: *(`/clear` is safe — `/gsd:resume-work` restores position from `HANDOFF.json` if you change your mind)* - Add an "Also available:" section with 1-3 alternatives where relevant Verification accumulates lots of test/UAT prose that won't help downstream; phase-end is a clean boundary for `/clear`. </output_format> --- **Source:** [`davepoon/buildwithclaude`](https://github.com/davepoon/buildwithclaude) → `plugins/gsd/skills/verify-work/SKILL.md`

Frequently asked questions