Adds spec-as-source enforcement to any project using spec-driven development
87
91%
Does it follow best practices?
Impact
82%
2.34xAverage score across 5 eval scenarios
Passed
No known issues
Every file listed in the targets: field of a .spec.md must begin with this header:
For Python files:
# GENERATED FROM SPEC — DO NOT EDIT DIRECTLY
# Source: specs/<spec-name>.spec.mdFor JavaScript/TypeScript files:
// GENERATED FROM SPEC — DO NOT EDIT DIRECTLY
// Source: specs/<spec-name>.spec.mdFor other file types, use the appropriate comment syntax.
Add the header as the very first line(s) of the file (after shebang or doctype if present) before writing any other content. Replace <spec-name> with the actual spec filename.