ralph-preflight

Pre-flight checks validate configuration, templates, and environment for TUI loops by detecting global CLAUDE.md conflicts, verifying prd.json fields, and enforcing template variable usage before execution starts.

TUI workflow startup failures often stem from configuration conflicts or missing prerequisites. A pre-flight check detects environment and global CLAUDE.md conflicts to ensure launch readiness before the loop begins.

Pre-flight validation for TUI loops checks project configurations, template variables, and runtime context. It ensures required fields in prd.json are present and detects conflicts to guarantee deterministic execution.

You need to run pre-flight checks after a PRD is created but before starting the TUI iteration. This ensures all prerequisites are in place and prevents wasted runs from setup errors.

Yes, pre-flight validation enforces required fields, template variable usage, and launch readiness checks across project, template, and runtime context to ensure deterministic execution of TUI loops.

Yes, the pre-flight check detects environment and global CLAUDE.md conflicts alongside template and prd.json validation, providing a post-check summary and guided launch commands to safely start the loop.