ss-sdd-preflight

To validate spec-driven-development readiness, run a preflight check that confirms your `.sublime-skills/config.yml` exists, passes validation, and verifies your git repository has an attached HEAD. This ensures later pipeline stages can rely on configuration and branch assumptions without surprises.

When your working tree is dirty during a spec-driven-development preflight check, the process warns you and asks for confirmation to proceed. This permissive dirty-tree handling ensures existing user changes remain untouched while still allowing the pipeline to continue if approved.

Spec-driven-development pipeline validation does not work on a detached HEAD state. The preflight checks verify that HEAD is attached to a named branch and will abort immediately if it detects a detached HEAD to prevent running stages in invalid environments.

You need to initialize a `state.json` shell to ensure a valid, commit-capable repository state for later pipeline stages. It atomically removes orphan state files from dead pipelines and creates a fresh minimal state file only after all hard checks pass.

The best way to prevent wasted work from misconfigured SDD bootstrap artifacts is to run a preflight validation gate. It confirms `validate-config.sh` passes and checks git repository status before drafting specs, aborting immediately if configuration is missing or invalid.