Get the smallest useful proof
New Blueprint projects use tryGuide: "when-testable". After Verify and any
required Check pass, the implementation handoff includes a compact Try It Now
section for work with a safe, meaningful direct observation.
It gives you one command or interaction, the exact expected result when practical, and the specific behavior you just observed. CLI tools get terminal output, libraries get a runnable example, APIs get a request and response, and UI work gets a route with visible results. File, configuration, and data changes use the exact artifact or state to inspect.
Run $check guide in Codex or /check guide in Claude Code after
implementation when you want the proof explicitly or need a deeper walkthrough.
The skill reads the current or most recently completed feature, fix, or rollback
and the project commands. For a rollback, it explains how to prove the removed
path is gone and how to spot a regression in unaffected behavior.
A deeper review guide includes
- The exact development command
- The route, screen, endpoint, or CLI entry point
- Inputs and clicks in order
- Expected visible results
- Edge cases worth checking
- Symptoms that would count as a failure
Review is not proof theater
Try It Now does not replace tests, Verify, /check, or user acceptance. It gives
the user an immediate observation, while the deeper guide focuses human
attention on visual quality, wording, interaction feel, and product behavior
that automated assertions cannot judge well.
Documentation-only edits and invisible internal changes do not get a fabricated proof. If there is no safe direct path, Blueprint states that plainly or omits the section according to the configured workflow.