
Activates when the user wants to evaluate and optimize the governance chain quality, generate business-layer evaluation criteria from documents, or run the autoresearch optimization loop on SKILL.md prompts. Use for governance self-improvement.
Activates when investigating bugs, failures, or unexpected behavior. Enforces root-cause analysis before implementation. Use for any bug, test failure, regression, or production incident.
Activates when tasks involve UI, interaction, layout, accessibility, performance, or visual design. Ensures visual decisions don't break semantic contracts.
Activates when writing code against upstream contracts. Ensures implementation stays within module boundaries and escalates design gaps instead of silently fixing them.
Activates when defining module contracts, boundaries, dataflow, or workflows. Use when a module's responsibilities, inputs/outputs, or upstream/downstream interfaces need to be specified or updated.
Orchestrates Context Governance role chain. Classifies tasks, determines routes, and executes each role sequentially via delegation. Use this as the entry point for any governed task in Hermes.
Activates when verifying implementation against contracts, when claiming work is complete, or when assessing whether tests actually prove contract satisfaction. Use for evidence-based acceptance.
Validates Context Governance compliance — task routing, protected artifact checks, receipt management, and pre-commit gates. For use with Hermes Agent.
Validates Context Governance compliance — task routing, protected artifact checks, receipt management, and pre-commit gates.
Activates when documents conflict, when historical mitigations are treated as baselines, when code is treated as design truth, when authority hierarchy needs adjudication, or when PROJECT_BASELINE has been created/updated and derived documents need to be generated or refreshed. Use for system-level truth arbitration and baseline derivation.