doc-itest-validator

Validate ITEST documents for subtype-specific schema, structure, traceability, contract, and interaction requirements.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "doc-itest-validator" with this command: npx skills add vladm3105/aidoc-flow-framework/vladm3105-aidoc-flow-framework-doc-itest-validator

doc-itest-validator

Purpose

Validate ITEST documents for subtype-specific schema, structure, traceability, contract, and interaction requirements.

Validation Schema Reference

  • ai_dev_ssd_flow/10_TSPEC/ITEST/ITEST_MVP_SCHEMA.yaml

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

  • ai_dev_ssd_flow/10_TSPEC/ITEST/ITEST_MVP_VALIDATION_RULES.md

Validation Checklist

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

  • Six required sections present and ordered

  • ITEST element IDs use TSPEC.NN.41.SS

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

  • Required subtype tags present (@ctr , @sys )

  • Contract compliance tables and interaction coverage are present

  • Sequence diagrams exist for complex interactions

  • CTR coverage matrix and TASKS-Ready claim are present

Commands

python ai_dev_ssd_flow/10_TSPEC/scripts/validate_itest.py docs/10_TSPEC/ITEST/ 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/ITEST/ITEST-NN_slug/ITEST-NN_slug.md --auto-fix python ai_dev_ssd_flow/scripts/validate_tags_against_docs.py --artifact ITEST-NN --expected-layers brd,prd,ears,bdd,adr,sys,req,spec --strict

Integration

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

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

Version History

Version Date Changes

1.0 2026-02-27 Initial ITEST validator with schema/structure/tag/contract checks and canonical script references

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 .

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

n8n

No summary provided by upstream source.

Repository SourceNeeds Review
General

google-adk

No summary provided by upstream source.

Repository SourceNeeds Review
General

doc-prd

No summary provided by upstream source.

Repository SourceNeeds Review
General

mermaid-gen

No summary provided by upstream source.

Repository SourceNeeds Review