Repository navigation
Run A Prose Pass
Note
Goal: Simplify a finished design doc (or any authored prose) with a second model, then verify nothing drifted before deploying the result.
Prereqs: the design plugin installed (Install crickets plugins); the agy CLI authenticated; a vault configured with your voice pack (agentm_config --vault-path).
The pass is two steps: Gemini simplifies, Claude verifies. A simplification pass run by the model that wrote the prose is an echo chamber — it cannot see the sentences only the author can parse. The prose-pass skill sends the document to Gemini (via agy) for the readability edit, then your agent verifies every guarded fact held before anything overwrites the original. It is the prose sibling of code-review's cross-review.sh.
Note
Already automatic for design docs and wiki pages. /design author runs this pass for you at Step 5 (ready-for-review) and again on review-pass entry — see Author a design. The wiki documenter agent runs it on every drafted page before its preview. You don't need the steps below for either flow; they already fold the pass into their own Document History bookkeeping and report the fallback if agy degrades. Use this page to run the pass by hand on other prose — a README, a doc outside those two flows, or anything you're simplifying standalone.
-
Settle the content first. Run the pass on a document whose meaning is final — a design at
Status: final, a page after a truth audit. The pass improves readability; it never decides what the document says. -
Write the fact-guard list. Three to eight lines, each a truth in this document that a simplifier could plausibly invert:
volatile decay only lowers retrieval rank — nothing is deleted inbox triage auto-applies, it is not a review gate re-audit triggers are conditions to revisit, never commitmentsThe list is mandatory — the script refuses to run without it. The first un-guarded pass introduced exactly these inversions.
-
Run the script:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prose_pass.py" wiki/designs/my-design.md \ --fact-guard guards.txt \ -o /tmp/my-design.revised.mdThe script assembles one prompt — task rules, your fact-guards, your voice pack inlined verbatim from the vault, the document — and sends it to
agyin a single call. Structure is enforced mechanically: frontmatter, headings, table layouts, and the Document History section must come back byte-identical, with one retry before it gives up. -
Verify and apply. Diff the revision against the original and work the
prose-passskill's checklist: every fact-guard held, technical claims spot-checked against the code they describe, operator-authored lines restored verbatim, banned vocabulary scanned. Apply corrections to the revised file. -
Deploy and record. Only after the checklist passes, copy the revision over the original and add a row to the document's Document History — one row per day, consolidated.
| Symptom | Cause | Fix |
|---|---|---|
PROSE-PASS-DEGRADED: agy CLI unavailable (exit 1) |
agy missing or unauthenticated |
Install/authenticate agy, or run the skill's Claude-only fallback pass |
PROSE-PASS-DEGRADED: vault unresolved / voice pack unresolved (exit 1) |
No vault path configured, or no voice kernel (standards/user-preferences.md) or overlay in the vault |
agentm_config --vault-path <path>, or pass --vault-path / --voice-kernel / --overlay explicitly |
a FACT-GUARD list is required (exit 2) |
No guards passed | Write the guard list (step 2); it is not optional |
argument --timeout: ... is not a Go duration (exit 2) |
--timeout got something agy can't read |
Pass seconds (300) or a Go duration (90s, 5m, 1h30m) |
structural contract violated twice (exit 2) |
The model kept rewriting structure | Re-run; if it persists, pass sections separately or fall back to the Claude-only pass |
| Revision reads generic, voice gone | Overlay didn't match the genre | Point --overlay at the right file under standards/voice/
|
- Author a design — write the document this pass polishes
- Review a change — code review — the code sibling of this pass
- Record an architectural decision — where meaning changes go (never through this pass)
- Manifest schema — skill primitive frontmatter reference
🔧 How-to
- Install plugins
- Run the development loop
- Using code review
- Provision a repo's wiki
- Declare a project's Architecture
- Maintain a wiki — wiki-watcher
- Review a change — code review
- In-flight decision review — /doubt
- Author a design
- Run a cross-model prose pass
- Run a named plan
- Run isolated tasks
- Configure main branch protection
- See every active plan
- Open a project by name
- Run a coordinator-directed worker team
- Install the vault backend
- Sync a project board