Inspects or updates validation stage for planned changes in current harness session, managing acceptance/regression checks, browser/observability evidence, blockers, and readiness.
From openarchenpx claudepluginhub done-0/openarche --plugin openarche/validateValidates CLI harness for software at given path or GitHub repo against HARNESS.md standards: directory structure, files, Click CLI, core modules, tests, and docs.
/validateValidates project structure, git config, build setup, code quality, CI/CD workflows, and best practices; reports issues, score, and recommendations with --path and --verbose options.
/validateValidates project implementation against scope and tasks documents using parallel subagents, producing validation_gaps.md with actionable remediation tasks.
/validateValidates cli-anything-web CLI at <app-path> against HARNESS.md standards across 11 categories (75 checks), reporting N/N pass/fail counts and fix suggestions for failures.
/validateValidates SonIA project operational integrity: checks kanban Markdown files, traceability, progress, UAT JSON, and optional GitHub sync. Reports verdict as approved, approved with warnings, or rejected.
/validateValidates plans, roadmaps, or proposals as ruthless CTO mentor, producing 8-section report with verdict, strengths, flaws, blindspots, and next steps.
Use this command to inspect or update the validation stage for the current harness session.
Required behavior:
.openarche/sessions/<task-id>/state.json.
Only create a separate note when the user explicitly asks for one.runbook.validation section and keep its structure stable.runbook.validation as the source of truth for:
runbook.validation and store any file evidence under .openarche/sessions/<task-id>/evidence/ instead of inventing a parallel format.When presenting the validation work, organize it into: