gos-critic-deck

To validate pitch deck slides, run a tool-grounded critique that checks slide outputs for missing CTAs, unsubstituted placeholders, and footer presence, returning a structured JSON report with remediation hints for each defect found.

Offline readiness validation for HTML pitch decks is a quality check that scans deck.html and slides-md directories to ensure all assets are locally embedded and functional without network connectivity, returning structured JSON results.

Automate quality gate checks for pitch deck generation by running validation scripts that enforce slide count, footer, CTA, and placeholder rules, using exit codes 0, 1, and 2 to signal PASS, FAIL, or missing folder to your CI pipeline.

Yes, you can use Python scripts to audit pitch deck outputs for consistency. The validation process applies five specific checks across deck.html and slides-md directories and generates a formal JSON validation record suitable for human audits.

A pitch deck validation report shows a missing folder error when the target deck directory cannot be located, which triggers an exit code 2. This indicates the validation scripts could not find the deck.html or slides-md directories to begin checking.

Yes, pitch deck validation checks both HTML and Markdown slide outputs. The quality gate process scans both the deck.html file and the slides-md directory to ensure consistent formatting, footers, and CTAs across all generated presentation formats.