Servo

Skills

9 in the Claude listing

• Close the booksBefore calling work done, reconcile it against its opening commitments — every acceptance criterion ticked, every invariant re-verified — with evidence, not assertion.
• Expert panelFor 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.
• Gather contextBefore 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.
• Scan projectOnce 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.
• Scope watchDuring 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.
• Seal planWrite 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.
• Servo flowThe servo process for a piece of work, phase by phase.
• Servo gateVerify 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.
• Shape specWrite 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.