jon-devlapaz Validation Planner
Use this skill to test whether the right thing was built for the intended use.
Workflow
- Restate the user need, intended environment, actors, and CONOPS scenario.
- Define validation scenarios in user/workflow language, not implementation language.
- Identify success signals: user-observable outcome, acceptance by stakeholder, task completion, or operational fit.
- Compare verified behavior against those scenarios; do not assume verification proves validation.
- Identify gaps between requirements compliance and intended-use success.
- Choose the smallest validation artifact: walkthrough, browser flow, screenshot, user script, demo, recorded trace, or reviewer checklist.
- Output a validation plan: need, scenario, environment, success signal, artifact, gaps, residual risk.
Source grounding
Start with references/source-grounding.md, then inspect Section 5.4 pages extraction/pages/page_109.md through extraction/pages/page_115.md and Appendix E pages extraction/pages/page_213.md through extraction/pages/page_214.md before making validation-specific claims.