anti-ceremony
GitHub防止流程冗余,聚焦可交付结果。通过快速审查或全量审计,拦截无实际消费者或缺乏独立证明的无效工作,确保进度与验收标准挂钩,拒绝制造控制性文档。
Trigger Scenarios
Install
npx skills add boshu2/agentops --skill anti-ceremony -g -y
SKILL.md
Frontmatter
{
"name": "anti-ceremony",
"consumes": [
"caller-outcome",
"proposed-process-work",
"proof-state"
],
"metadata": {
"tier": "judgment",
"effects": [],
"stability": "experimental",
"disposition": "keep_specialist",
"capabilities": [
"guard_anti_ceremony",
"audit_anti_ceremony"
],
"dependencies": [],
"canonical_status": "canonical"
},
"produces": [
"anti-ceremony-decision"
],
"practices": [
"lean",
"evidence-based-development"
],
"context_rel": [],
"description": "Guard outcome work against process overhead. Triggers: RPI pre-Plan guard; explicit \"full anti-ceremony audit\" requests.",
"hexagonal_role": "supporting",
"user-invocable": true,
"output_contract": "artifact-free CONTINUE or STOP decision with reason, frozen_outcome, parked_process_work, remaining_proof, and stop_condition",
"skill_api_version": 1
}
Anti-Ceremony
Keep work tied to the caller-visible outcome and the proof still needed for it. The default guard is a single, artifact-free judgment before RPI Plan; the full honesty audit runs only on an explicit "full anti-ceremony audit" request.
Prompt
Quick guard. Outcome: "ao gate check lists the probe-coverage row". Proposed
process work: a coverage dashboard and a second audit pass. Remaining proof:
the gate row, green in CI. Stop condition: that gate passes on main.
It's working if
- The response is the YAML shape below and nothing else: no file appears
under
.agents/, and no tracker write is issued. reason:is one sentence, andparked_process_work:names the dashboard-shaped items.- A full audit appears only after the caller wrote
full anti-ceremony audit.
Quick guard
- Freeze the caller-visible outcome in one short statement.
- Park proposed process work that has no concrete consumer, gated subject or release decision, observed defect, or retirement condition.
- Name the implementation or independent proof still missing.
- Name the condition that ends this traversal.
- Return
STOPwhen the traversal would only create control artifacts or the frozen outcome is already sufficiently proved; otherwise returnCONTINUE.
Progress needs evidence tied to acceptance or a named blocking uncertainty.
Digest movement, finding counts, and additional reviews alone earn no credit.
Informative red can justify a different experiment inside an explicitly selected
outer goal's unchanged acceptance and allowance; repeated no-information work
cannot. Keep required independent proof in remaining_proof, including every
necessary unresolved finding. Apply Validate's effect-based risk rule to the
cost of proof; never weaken the exact-subject or all-acceptance PASS bar.
Perform the guard exactly once in memory. Parking is a field in the response, not a tracker or delivery mutation. Return this shape:
decision: CONTINUE | STOP
reason: <exactly one sentence>
frozen_outcome: <nonempty string>
parked_process_work: [<work item>, ...]
remaining_proof: [<proof item>, ...]
stop_condition: <nonempty string>
The two lists contain strings and may be empty. Done when every field is present and the decision explains whether one RPI traversal earns its cost.
Full honesty audit
Run this mode only when the caller explicitly requests it. Examine each named control artifact or ceremony step for its consumer, gated subject or release decision, observed defect, and retirement condition; return concise keep, park, or drop findings in the response.
Boundary
Before returning the decision, read boundaries.md in the rpi skill's
references directory. On malformed or missing inputs, return STOP with
the missing field named in the one-sentence reason.
Version History
-
8061085
Current 2026-09-09 05:15
增加边界检查以读取参考文件;强化对无界执行和修复循环的限制,要求进度必须与验收挂钩并区分新缺陷与回归。
- 7b07a7d 2026-08-19 21:58


