Menu
Validate built features through conversational UAT
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | cds-verify-work |
| description | Validate built features through conversational UAT |
| argument-hint | [phase number, e.g., '4'] |
| allowed-tools | ["Read","Bash","Glob","Grep","Edit","Write","Task"] |
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 /cds-execute-phase
<execution_context> @$HOME/.claude/cds-workflow/workflows/verify-work.md @$HOME/.claude/cds-workflow/templates/UAT.md </execution_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.
Add an idea to the backlog parking lot (999.x numbering)
Systematic debugging with persistent state across context resets
Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
Build, query, and inspect the project knowledge graph in .planning/graphs/
Query, inspect, or refresh codebase intelligence files in .planning/intel/
