anti-ceremony
FeaturedGuard outcome work against process overhead. Triggers: optional "quick guard"; explicit "full anti-ceremony audit" requests.
AI & Automation 434 stars
40 forks Updated today Apache-2.0
Install
Quality Score: 97/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Anti-Ceremony
Keep work tied to the caller-visible outcome and the proof still needed for it.
The optional guard is a single, artifact-free judgment when selected; the full
honesty audit runs only on an explicit "full anti-ceremony audit" request.
## Prompt
```text
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, and `parked_process_work:` names the
dashboard-shaped items.
- A full audit appears only after the caller wrote `full anti-ceremony audit`.
## Quick guard
1. Freeze the caller-visible outcome in one short statement.
2. Park proposed process work that has no concrete consumer, gated subject or
release decision, observed defect, or retirement condition.
3. Name the implementation or independent proof still missing.
4. Name the condition that ends this traversal.
5. Return `STOP` when the traversal would only create control artifacts or the
frozen outcome is already sufficiently proved; otherwise return `CONTINUE`.
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 ex...
Details
- Author
- boshu2
- Repository
- boshu2/agentops
- Created
- 10 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
scope-guard
Judgment check before calling substantial work done or proposing a commit. Use before "done", before committing more than a trivial change, and whenever you notice yourself building something nobody asked for. The judgment layer above the automated gates, not a duplicate of them.
2 Updated 4 days ago
Tradebaas AI & Automation Listed
audit
Use when completed work or artifacts need a read-oriented inspection for drift, inconsistency, omissions, or unsupported claims. Not for implementing fixes, producing the primary artifact, or replacing execution-stage verification.
7 Updated today
dmlguq456