prompt-template-review

Placeholder validation detects unreplaced {PLACEHOLDER} tokens in pipeline prompt templates by scanning files in scripts/build/phases and specified templates like v6-write.md, then generating a structured findings report of all unresolved tokens.

Cross-template consistency checking identifies contradictions between related prompt templates and ensures instructions remain consistent across pipeline phases, preventing conflicting directives from derailing automated workflows and model interactions.

Checking prompt templates for stale instructions involves scanning pipeline template files to identify outdated or obsolete directives that could derail automated workflows, then compiling the results into a structured findings report for remediation.

Yes, you can validate a specific file such as v6-write.md alongside all templates in scripts/build/phases by running the review process to check placeholder coverage and cross-template consistency across the entire specified scope.

The best way to automate prompt template validation for CI pipelines is to run a review tool against all templates in scripts/build/phases that checks for unreplaced placeholders, contradictions, and stale instructions, outputting a structured report to ensure reliable prompt generation.

Automated workflows fail due to contradictions between prompt templates because conflicting instructions across pipeline phases cause inconsistent model interactions, which validation checks identify by scanning for cross-template inconsistencies before execution.