| name | ferrox-verify-work |
| description | Something was built and you want to confirm it works, by trying it rather than trusting it |
| argument-hint | [phase number, e.g., '4'] [--ws <name>] |
| allowed-tools | ["Read","Bash","Glob","Grep","Edit","Write","Agent"] |
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 /ferrox-execute-phase
<execution_context>
@/.claude/ferrox-core/workflows/verify-work.md
@/.claude/ferrox-core/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 phase
Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.
Execute end-to-end.
Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
