doc-stest-validator

Purpose

Validate STEST documents for subtype-specific schema, structure, traceability, and deployment-smoke gate requirements.

Validation Schema Reference

• ai_dev_ssd_flow/10_TSPEC/STEST/STEST_MVP_SCHEMA.yaml

• ai_dev_ssd_flow/10_TSPEC/STEST/STEST-MVP-TEMPLATE.md

• ai_dev_ssd_flow/10_TSPEC/STEST/STEST_MVP_VALIDATION_RULES.md

Validation Checklist

• Nested folder rule (STEST-NN_{slug}/STEST-NN_{slug}.md )

• Six required sections present and ordered

• STEST element IDs use TSPEC.NN.42.SS

• Required cumulative tags present (@brd ..@spec , optional @ctr )

• Required subtype tags present (@ears , @bdd , @req )

• Timeout budget markers are present (max 300s or <=300s )

• 100% gate markers are present (Target: 100% or 100% quality gate )

• Rollback procedure requirement is explicit (every test must have rollback procedure)

• Binary pass/fail criteria are explicit for critical paths

Commands

python ai_dev_ssd_flow/10_TSPEC/scripts/validate_stest.py docs/10_TSPEC/STEST/ bash ai_dev_ssd_flow/10_TSPEC/scripts/validate_all_tspec.sh docs/10_TSPEC/ bash ai_dev_ssd_flow/10_TSPEC/scripts/validate_tspec_quality_score.sh docs/10_TSPEC/ python ai_dev_ssd_flow/scripts/validate_cross_document.py --document docs/10_TSPEC/STEST/STEST-NN_slug/STEST-NN_slug.md --auto-fix python ai_dev_ssd_flow/scripts/validate_tags_against_docs.py --artifact STEST-NN --expected-layers brd,prd,ears,bdd,adr,sys,req,spec --strict

Integration

• Invoked by: doc-stest , doc-stest-autopilot , doc-stest-audit

• Feeds into: doc-stest-audit , doc-stest-fixer

Version History

Version Date Changes

1.0 2026-02-27 Initial STEST validator with schema/structure/tag checks and strict deployment-gate validation rules

Implementation Plan Consistency (IPLAN-004)

• Treat plan-derived outputs as valid source mode and verify intent preservation from implementation plan scope/objectives.

• Validate upstream autopilot precedence assumption: --iplan > --ref > --prompt .

• Flag objective/scope conflicts between plan context and artifact output as blocking issues requiring clarification.

• Do not introduce legacy fallback paths such as docs-v2.0/00_REF .