lens-lifecycle

Run lifecycle_ops.py with the validate-phase command, passing --project-root, --feature-id, and --phase. It checks that all required artifacts for that phase exist in the feature's docs directory and returns a pass or fail status with missing files listed.

Use the suggest-next command with the feature ID. The script reads feature.yaml, determines the track (full or express), checks predecessor completion, and returns the recommended next phase or routes completed features to lens-doctor.

The full track runs preplan, businessplan, techplan, finalizeplan, then dev. The express track skips to expressplan, finalizeplan, then dev, requiring consolidated business-plan, tech-plan, and sprint-plan documents instead of separate artifacts.

Yes, but only with the --force flag on advance-phase, intended for recovery scenarios. Without it, advancement is blocked until all required files and glob patterns for the phase exist in the feature's docs directory.

No. The script is a clean-room implementation that never imports or invokes lens.core. It uses only the Python standard library and reads feature state directly from docs/features/<feature-id>/feature.yaml.