Process discipline for AI agents: ground-truth oracles, non-colluding gates, deterministic plans. A Claude Code plugin.
Skill Claude CodeCodex
Before calling work done, reconcile it against its opening commitments — every acceptance criterion ticked, every invariant re-verified — with evidence, not assertion. Use when about to claim a task is complete or before merging.
Skill Claude CodeCodex
For a decision with no ground truth yet (a real design fork), convene the relevant domain experts plus a mandated dissenter, weigh the options, and let the human decide. Use instead of deciding alone or asking the human one question at a time.
Skill Claude CodeCodex
Before working on a task, pull the relevant slices of the project's ground truth from the manifest, write a short context brief, and confirm it with the human in one batch. Re-run at each phase boundary, not just at the start.
Skill Claude CodeCodex
Once per project, discover its manifest — where the project's ground truth lives and which domains (experts) it has — by scanning it, then propose a manifest for the human to accept or adjust. Use when a project has no .servo/manifest.yaml yet, or to refresh a stale one.
Skill Claude CodeCodex
During execution, continuously diff the work in progress against the intent of the issue (the scope oracle), so drift is caught in flight rather than at review. Use while implementing a plan, especially across many steps.
Skill Claude CodeCodex
Write a plan that runs anywhere — closed (zero open decisions), pinned to a machine-checkable acceptance oracle, and written for the weakest executor you intend to use — then gate it against the spec. Use after the spec passes its gate.
Skill Claude CodeCodex
The servo process for a piece of work, phase by phase. Use at the start of any non-trivial task to know which phase you are in and which skill to run next.
Skill Claude CodeCodex
Verify an artifact (a spec, a plan, a diff, a claim) against a named oracle from the project manifest, using a reviewer that did not produce it. Returns GO / FIX / STOP. Use before accepting a spec or plan, or before merging.
Skill Claude CodeCodex
Write a spec that carries its own guardrails — it embeds the invariants it must not break and names the oracles it will be judged against — then gate it. Use after the design forks are decided and before writing a plan.