artifact-conventions

To maintain cross-artifact traceability when editing spec files, enforce preservation rules for cross-referenced IDs, priorities, and gating state to prevent accidental corruption of linked artifacts during edits.

Frontmatter validation rules for spec and plan artifacts require consistent frontmatter structure and specific section presence to ensure artifact integrity and governance across the feature workspace.

Preventing accidental changes to gating state in feature specs requires enforcing non-destructive edits and preservation conventions, protecting critical cross-referenced state values from being overwritten during routine artifact updates.

You need specification governance conventions for feature artifacts when editing files under specs/<feature-folder>/ to prevent changes to IDs, priorities, and gating state, ensuring consistency and traceability across the feature workspace.

Artifact convention enforcement works with existing spec.md and plan.md files by applying preservation, format, and section rules automatically when editing, guarding cross-artifact references without requiring file migration.