Handbook
Wizard 201 — Repair stage
Mission mode: process drift, inconsistent artifacts, or a blocked stage.
What it is
Mission mode: process drift, inconsistent artifacts, or a blocked stage.
Parent: Wizard 201 — Mission modes.
When to use it
When recheck or review keeps surfacing the same class of gap and you need a corrective posture.
Outcome
A corrective run plan and recheck you can track to closure.
When not to use it
Do not use Repair for new discovery when no foundation exists — Start from idea or Assess current project fits better. If the blocker is purely tooling (server, save errors), fix the environment first (Troubleshooting).
Inputs you need before the session
| Input | Why |
|---|---|
| The recurring failure class (from recheck or review) | One corrective theme per session |
| Risk acceptance (what can ship with a documented gap) | Avoids infinite repair loops |
| Owner per gap | Clear accountability in Run plan |
Map to Wizard 101
In Wizard 101, steps 10–11 (Review & generate, Recheck / repair) are central here. You may still touch Run plan (step 9) to reorder work around fixes.
Common mistakes
| Mistake | What to do |
|---|---|
| Repair without root cause | Name the class of failure (not one-off typos) |
| Too many owners | One owner per gap class |
| Skipping explicit risk when deferring | Record accepted gaps with dates |
Example scenario (mission mode)
| Starting situation | Recheck keeps failing on the same gap; delivery pressure is high. |
| Action taken | Use Repair posture in Mission; prioritize Recheck / repair steps and one corrective owner per gap class. |
| Expected result | Fewer open inconsistencies; recheck passes or gaps are explicitly accepted with risk recorded. |
| What to check | Same failure does not recur on the next recheck without a documented exception. |