| name | update-wizard |
| description | Smart update workflow for Codex SDLC repos — compare current state against wizard expectations, preserve customizations, and update selectively. |
Update Wizard
Purpose
You are a guided update assistant. Your job is to show what changed, detect drift, and help the user adopt updates without flattening their customizations.
Do not blindly overwrite files.
Version boundary: $update-wizard updates repo artifacts using the wizard version already installed in the active Codex skill/session. It does not self-update the npm package. To consume the newest published package first, tell the user to run npx codex-sdlc-wizard@latest update from the repo, then restart or resume Codex so refreshed skills/hooks/config load.
Package upgrade preflight
Before scanning repo drift, correct the package boundary in plain language:
- Package upgrade means consuming the newest published
codex-sdlc-wizard package.
- Repo repair/sync means inspecting and repairing local SDLC artifacts with the wizard already loaded in this Codex session.
$update-wizard performs repo repair/sync. It does not self-update the active Codex session or npm package.
When network is available, compare the current installed skill/package version against npm latest:
npm view codex-sdlc-wizard version
If the local package may be stale, the user asked for latest, or the installed version trails npm, give this package-upgrade command before repo repair:
npx codex-sdlc-wizard@latest update
If network is unavailable, say the latest package status could not be verified and still provide the @latest command as the safe upgrade path. After any package upgrade or repo artifact repair, tell the user to restart/reopen Codex so refreshed skills/hooks/config load.
Reasoning policy
Default to xhigh in this repo. Update work is maintenance architecture, and customized drift makes lower-effort passes too risky by default.
Scope guard
Update owns the wizard surface: repo metadata, Codex integration artifacts, hooks, skills, helper scripts, and SDLC docs.
During update, do not edit application code, product logic, or application tests. Verification is diagnostic by default: if tests or validation fail outside setup-managed files, summarize the failures and stop. Ask the user before switching from update into implementation work, or hand the remediation to $sdlc.
Only auto-fix failures that are directly caused by wizard drift, such as broken hook paths, missing installed skills, contradictory generated docs, stale helper scripts, or Windows hook config that still points at Bash scripts.
Canonical SDLC entrypoint: $sdlc. /sdlc is historical shorthand for the missing slash-command idea, not an invocation command. Do not create adapter-specific SDLC aliases as second user-facing workflows.
Mandatory first action
Read the local repo context first:
AGENTS.mdREADME.mdROADMAP.mdSDLC-LOOP.mdSTART-SDLC.mdPROVE-IT.mdTESTING.mdSDLC.mdGOALS.md when tracked by the manifest as an optional active-scope contract
If running inside codex-sdlc-wizard, also read:
README.mdCODEX_ADAPTER_PLAN.md
Execution checklist
Step 1: Read installed state
Identify what exists now:
- repo-local SDLC docs
- active hooks and hook config
- installed Codex skills
- customizations that differ from wizard defaults
Step 2: Compare against expected surface
Expected Codex SDLC surface includes:
sdlcsetup-wizardupdate-wizardfeedback- repo-local SDLC docs as appropriate
- repo-local
.codex/config.toml model settings that match the selected wizard profile
- hook config and scripts
Group findings as:
- match
- missing
- customized
- drift / broken
Platform-specific hook wiring is drift / broken, not a customization to preserve. On Windows, .codex/hooks.json that still points at Bash hook scripts is broken. On macOS/Linux, .codex/hooks.json that still points at powershell.exe is broken. Repair both cases to the universal Node hook entrypoints.
If .codex-sdlc/model-profile.json or SDLC.md says one model profile but .codex/config.toml still inherits a different user/global model, classify that as drift. Preserve unrelated config keys and only patch the wizard-owned top-level model, model_reasoning_effort, review_model, and [features].hooks settings. Treat active [features].codex_hooks as deprecated drift; the exact replacement is [features].hooks = true. Migrate deprecated codex_hooks entries away instead of preserving duplicate feature flags. Explain that mixed is wizard policy, not a native Codex mode, and that project config only loads after the repo is trusted.
Step 3: Show update plan first
Before applying anything, tell the user:
- what is current
- what is missing
- what changed upstream or in the local wizard
- which files are customized and should be preserved
Use human-readable summaries, not giant raw diffs by default.
Step 4: Apply updates selectively
Missing files can be installed or created.
Customized files should be merged or skipped intentionally.
Never replace strong repo-local docs just to make them look more like the wizard.
If GOALS.md is tracked in the manifest, preserve its customization by default and repair it only when missing, broken, or explicitly forced. It is the optional active-scope contract for long-running work; ROADMAP.md stays backlog/history.
Step 5: Verify
After updates, verify:
- skills exist where expected
- hooks still match the intended quiet enforcement set
- repo-local docs are internally consistent
- customized files were preserved when requested
- active hook config uses the universal Node hook entrypoints instead of OS-specific Bash or PowerShell commands
This verification is diagnostic for product behavior. If a failing command points at application code or application tests unrelated to wizard-managed changes, do not edit application code to force update green. Report the failure, identify why it appears outside update scope, and ask whether to continue under $sdlc.
Step 6: Restart and next steps
If skills, hooks, hook config, or helper scripts were installed or repaired, tell the user to exit and reopen Codex in this repo so the active session reloads them. Tell them: you do not need to rerun update just for that restart. If they closed an interrupted handoff and Codex printed a resume id, recommend codex resume -m <model> -c 'model_reasoning_effort="xhigh"' <session-id> for model-explicit continuation, or plain codex resume <session-id> when they want config-driven startup. If they normally say yolo, give the full-trust variant with --dangerously-bypass-approvals-and-sandbox and say full-auto is not full-trust.
Rules
- Never overwrite customizations blindly.
- Prefer merge or extension over replacement.
- Explain drift clearly.
- If the repo is effectively uninitialized, recommend running
$setup-wizard instead.
- During update, never cross into product remediation without explicit user consent.
