Docs

/ validate

Run user acceptance testing on a completed implementation before closing.

The /validate command runs user acceptance testing. It presents each acceptance criterion with testing guidance and waits for you to confirm whether the implementation meets your expectations.

Usage

agent chat 
/validate
agent chat 
test this
agent chat 
QA ENG-145

Or after reviewing the implementation yourself:

agent chat 
looks good, approve it

What Happens

  1. Load the issue: Reads the acceptance criteria and implementation details
  2. Present each criterion: Walks through every acceptance criterion with specific testing guidance
  3. Wait for feedback: You test and confirm each item
  4. Process results: Based on your feedback, either approves or flags issues

Outcomes

Approved

If everything passes, the QE agent confirms with you, then adds a "QE Approved" comment to the issue. The issue is now ready for /close.

Issues Found

If any criterion fails validation, the QE agent documents the issues and transitions the issue back to Implementing for fixes.

Important

The QE agent never closes issues. That's the PM's job via /close. Validation ends with either a "QE Approved" comment or a transition back to Implementing. The close step is deliberately separate.

When to Use It

After /review has passed. The issue should be in the Testing state. This is the final check before closing, your chance to confirm that what was built matches what you asked for.

Related Commands

  • /review: Code review before validation
  • /close: Close after approval
  • /implement: Back to implementation if issues are found