Skip to main content

Redo & Exit

Redo any stage​

Any stage can be redone at any time — even after approval. This is always allowed and is never blocked.

  • Type redo {n} (e.g. redo 2) from the Main Menu or during any stage
  • System re-runs the stage from the beginning using current session context
  • Downstream stages are flagged (⚠ may need re-approval) but not deleted
  • Previous artifact files are preserved — new versions appended with a timestamp suffix
  • After redo completes, Main Menu is re-displayed
warning

Redoing Stage 1 (PRD) may cause downstream stages to drift. The system flags but never auto-deletes dependent artifacts.

Exit & save​

EXIT is available everywhere. It always appears in its own visually distinct ╔══╗ section — never mixed with action options.

Exit PathTriggerBehaviour
Main MenuSelect option 10Confirmation dialog → Save session + all artifacts → Goodbye message
During QuestionType exitConfirmation → Generate partial artifact (TBD gaps marked) → BA approval prompt → Goodbye
During ApprovalType EConfirmation → Mark stage as pending-approval in session.md → Goodbye
Terminal Close (✕)Window close / Ctrl+Cclose-guard.ps1 intercepts → Native Windows dialog → Auto-save via Stop hook (stop-hook.ps1)
info

After partial save on EXIT during questions, the system shows a BA approval prompt before goodbye — so the BA can approve the partial artifact and allow downstream stages to proceed. Options: A (Approve+exit), R (Reject+exit), S (Skip/stay locked).

tip

Downstream stages are NOT blocked by TBD gaps in partial artifacts. Exception: the 5-step intake sequence is mandatory and cannot be partially saved.