Files
markitect-main/roadmap
tegwick a969c5de47 feat: add semantic document validator for x-markitect extensions
Implements semantic validation to complement existing structural validation:

Phase 1 & 2 Complete:
- SemanticValidator: Main validator orchestrating sub-validators
- SectionValidator: Enforces section classifications (required, recommended,
  optional, discouraged, improper) from x-markitect-sections
- ContentValidator: Validates content patterns, forbidden patterns, and
  quality metrics (word counts, sentence counts) from x-markitect-content-control

Features:
- Pattern matching with regex for required/forbidden/discouraged patterns
- Word count and sentence count validation
- Detailed error reporting with severity levels (ERROR, WARNING)
- Support for section alternatives (e.g., FLAGS vs OPTIONS)
- Comprehensive test coverage (16 tests, 100% passing)

Architecture:
- Complements existing SchemaValidator (structural AST validation)
- Clean separation: validators/ package for modular validators
- Semantic validation focuses on x-markitect-* extensions
- LinkValidator planned for Phase 3 (optional --check-links)

Next: Phase 4 - CLI integration to enhance 'markitect validate' command

Workplan: roadmap/20260106-semantic-document-validation/WORKPLAN.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-06 03:24:32 +01:00
..
2026-01-05 20:37:18 +01:00

MarkiTect Project Roadmap

This roadmap directory contains planning directories for roadmap topics.

  • When starting to implement a topic its directory will be timestamped
  • If implementing multiple topics in parallel use branches
  • Keep current state of what's next to implement in TODO.md
  • See ../history directory for closed topics

Purpose

This planning documentation serves multiple purposes:

  1. Implementation State Awareness: Allow for recovery after breaks or breakdowns
  2. Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
  3. Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
  4. Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized

xxx