ferrox-verify-work

User acceptance testing validates built software through conversational end-to-end testing, checking functionality step by step from a real-user perspective before shipment. You interact with the system in plain text to confirm the feature behaves correctly.

Conversational UAT tests software functionality one step at a time using plain text interaction. It helps confirm that a built feature actually works from a user's perspective instead of relying on a superficial checklist or model confidence.

Regression testing progress survives context loss by recording outcomes in a persistent, phase-specific UAT markdown file. This ensures verification state remains intact across active sessions for reliable handoff and continued diagnosis.

Yes, when problems appear during phased feature verification, the system identifies gaps and prepares a verified fix path. It applies workflow-guided diagnosis to generate phase-specific markdown output for the next execution phase.

The best way to confirm readiness for shipment is running end-to-end acceptance checks after a developer finishes a phase. This validates the behavior thoroughly and captures results in a corresponding UAT file before moving forward.

Software verification fails after context loss if outcomes are not recorded persistently. This skill prevents that by saving testing progress in a phase-specific UAT markdown file, ensuring reliable handoff and state survival across sessions.