feature-validation

To generate a validation checklist for a Flutter feature slice, use a tool that reads your existing prd.md, plan.md, and requirements.md to output a validation.md file with manual UX test scenarios and a code review checklist.

A feature slice validation checklist should include manual UX test scenarios, a code review checklist for verifying technical requirements in the diff, and project-wide build, localization, analysis, and test commands.

You can create manual UX test scenarios from requirements by converting them into concrete, observable test steps that a reviewer or tester can run by hand against the running Flutter application.

Yes, you need prd.md, plan.md, and requirements.md files in the target folder before generating a validation.md file to ensure proper requirement traceability and concrete acceptance criteria coverage.

Yes, this approach works for acceptance testing in Flutter projects by generating concrete acceptance criteria and project-wide verification checks that satisfy requirement traceability before merging a change.

The best way to add traceable acceptance criteria is to generate a validation.md document that maps existing technical requirements to inspectable code review items and manual UX test scenarios for the feature slice.