forge-plan

A validation plan defines step-level PASS criteria by discovering user journeys across web, API, mobile, and CLI surfaces, specifying required evidence types like screenshots, API responses, and logs for reproducible end-to-end testing.

Journey discovery for test planning scans code and project artifacts to enumerate user-facing journeys across web, API, mobile, and CLI surfaces, enabling coverage analysis to identify uncovered areas and generate additional testing scenarios.

Evidence collection requirements for API and web validation specify exact evidence types needed for verdicts, such as screenshots, API responses, console logs, and build output, ensuring reproducible evidence collection during systematic end-to-end validation.

You can merge validation perspectives from user advocacy, security, and QA into a consensus plan, combining multiple viewpoints to produce a unified validation plan with comprehensive journey coverage and step-level PASS criteria.

This validation planning approach works for mobile apps and CLI projects by discovering user journeys and defining PASS criteria across web, API, mobile, and CLI surfaces, preparing teams for systematic end-to-end validation and evidence collection.

Journey-based validation plans replace ad hoc testing by organizing discovery and requirements into reproducible plans with clear PASS criteria and verifiable evidence, ensuring teams validate systems through real interfaces rather than relying on mocks.