What problem does it solve? It prevents unverified or incomplete work from being promoted into the canonical spec by acting as an independent checkpoint that judges claims against actual evidence rather than trusting checked boxes or code that merely looks right. ## Core Features & Use Cases - Evidence-based validation: Judges each scenario in scenarios.feature against verification.md, automated tests, or confirmed manual checks, marking anything unproven as NÃO VERIFICADO. - Test discipline audit: Detects deleted, skipped, or loosened tests via git diff, verifies scenario-to-test coverage, and checks TDD ordering when the plan requires it. - Actionable fail loop: On failure, writes concrete correction tasks into tasks.md with an incremented attempt counter so implementation can resume without deadlock. - Use Case: After a cycle's tasks are all checked and verification.md exists, run validation to produce validation.md with a pass/fail result before promoting the spec. ## Quick Start Ask the assistant to validate the current cycle by saying "valida o ciclo" once all tasks except the promote task are checked and verification.md exists.
