spec-lint-implementation-plan

You can lint an implementation plan by validating its YAML frontmatter, exact gate definitions, and single precedence ladder to prevent weakening of contract thresholds and detect split-brain conflicts.

Split-brain conflict detection is a safety lint mechanism that identifies conflicting gate rules, legacy text, or bypass attempts within an implementation plan to prevent weakening of contract gates.

Enforce gate canonicalization by requiring precise gate definitions including inputs, comparators, thresholds, durations, and exit criteria, and mapping explicit tests to each gate in the plan.

Yes, the safety lint requires YAML frontmatter with name and description, exact gate definitions, a single precedence ladder, and documented rollback, test, and artifact requirements to pass validation.

If your plan lacks documented rollback and artifact paths, the fail-closed safety lint will reject it by flagging missing artifact governance, invalid write order, and incomplete safety gate prerequisites.