create-rule
Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project…
@coco-researchInstall SkillDevelopment
Skill
/gsd-verify-work
Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase.
Claude Code
$ npx -y skills add coco-research/coco --skill gsd-verify-work --agent claude-code
Codex
$ npx skills add coco-research/coco --skill gsd-verify-work -a codex -y
Cursor
$ npx skills add coco-research/coco --skill gsd-verify-work -a cursor -y
Gemini CLI
$ npx skills add coco-research/coco --skill gsd-verify-work -a gemini-cli -y
GitHub Copilot
$ npx skills add coco-research/coco --skill gsd-verify-work -a github-copilot -y
OpenCode
$ npx skills add coco-research/coco --skill gsd-verify-work -a opencode -y
Windsurf
$ npx skills add coco-research/coco --skill gsd-verify-work -a windsurf -y
SKILL.md
gsd-verify-work.SKILL.mdname: gsd-verify-work
description: "Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase."
argument-hint: "[phase number, e.g., '4']"
allowed-tools:
- Read
- Bash
- Glob
- Grep
- Edit
- Write
- Task<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> @$HOME/.claude/get-shit-done/workflows/verify-work.md @$HOME/.claude/get-shit-done/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 @$HOME/.claude/get-shit-done/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>
Read more
name: gsd-verify-work
description: "Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase."
argument-hint: "[phase number, e.g., '4']"
allowed-tools:
- Read
- Bash
- Glob
- Grep
- Edit
- Write
- Task<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> @$HOME/.claude/get-shit-done/workflows/verify-work.md @$HOME/.claude/get-shit-done/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 @$HOME/.claude/get-shit-done/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>
Ships withcoco
495 personas across 13 departments, 229 skills[^installed] and 388 commands in the full catalog (coco 1.9.0, 2026-10-21). Agent skills, slash commands and subagents for Claude Code, Cursor, Codex and other AI coding agents.
796200 skills53 agents
Stars on GitHub
Momentum
- stars in total
- 796
Other skills on coco.
@coco-researchInstall Skillcreate-skill
Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill,…
@coco-researchInstall Skillcreate-subagent
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific…
@coco-researchInstall Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills…
@coco-researchInstall Skillupdate-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences,…
@coco-researchInstall Skillagent-lightning
Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent…
@coco-researchInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about gsd-verify-work.
- Which coding agents can use gsd-verify-work?
- gsd-verify-work installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.