Handbook
Wizard 301 — Review and recheck
Review & generate as a gate, and Recheck / repair for consistency.
What it is
Review & generate as a gate, and Recheck / repair for consistency.
Parent: Wizard 301 — Advanced usage.
Review vs recheck
| Stage | Your job |
|---|---|
| Review & generate | Read artifacts against upstream notes; fix the session and regenerate instead of only editing preview text |
| Recheck / repair | Resolve consistency failures or explicitly accept gaps with rationale |
Tie-in: The worked example session on Wizard 301 — Advanced usage shows Review catching duplicate risk owners and Recheck failing until the session notes and regeneration align — not a cosmetic text fix.
Step-by-step usage (typical)
- Review & generate — Read generated artifacts against your session notes. If something is wrong, fix the session (steps or notes) and regenerate; do not only patch preview text if the underlying notes are stale.
- Recheck — If the UI lists inconsistencies, either fix them in place or document why a gap is accepted (owner, date).
- Repair loop — If the same gap reappears, switch posture toward Wizard 201 — Repair stage in a follow-on session rather than clicking through repeatedly.
UI affordances (plain language)
- Review is the quality gate before exports.
- Recheck is the consistency gate — treat failing recheck as signal, not nagging.