git:20261016.fe5bc0b to git:20261017.d4a809d

27 added, 41 removed. Audit A to A.

---

name: wuwei-rules

- description: How work runs under WUWEI, the process auditor. Use when unsure what done means, why a call was refused, whether to ask the owner, or how to pull the andon cord.

+ description: How work runs under WUWEI, the process auditor. Use when unsure what done means, why a call was refused, whether to ask the owner, or how to pull the andon cord. Not for running the day (/wuwei-run), a watch pass (/wuwei-watch) or the close (/wuwei-close); those skills act, this one explains.

---

# Working under WUWEI

WUWEI reads what you produce and says what is missing; it never prescribes the command. Use git,

gh and the repository's tools directly. `wuwei status` shows every open item's gaps;

`wuwei evidence owner/repo#n` shows one PR's.

- ## Done means evidence

- Only safety gaps (tests, gates, CI, review threads, owner review) hold a merge or show on the board.

- The rest is process fit: follow it, and the merge records any misfit for the retro.

- - The body keeps the repository's PR template sections and ends with the WUWEI footer, filled from

- `wuwei --version` and `wuwei plan show <id>`:

- `` <sub>[WUWEI <version>](https://taoq-ai.github.io/wuwei/) · Item `<id>` · <title> · Goal <G-n> · Tier <tier></sub> ``.

- - A test is in the diff, or a `No test: <reason>` line explains why none can hold the change.

- - The diff stays under about 400 changed lines (generated files aside), or a `Size: <reason>` line

- says why it cannot be split.

- - At `full` or on `owner_paths`, a `Rollback: <how to undo>` line.

- - At `standard` and `full`, when the repository has a spec engine, its steps are done by their artifacts

- at the head: spec-kit `spec.md`, `plan.md`, `tasks.md` all checked (full adds `## Clarifications`, an

- `analysis.md` with no open CRITICAL or HIGH, checked checklists); OpenSpec `proposal.md`, a capability

- spec, `tasks.md` all checked.

- - The gates the diff needs passed at the draft head before the PR turned ready (`gh pr ready` waits for them).

- The tier is the ceiling: docs need none; code quality; at standard, risky or owner paths add

- security and a wide change adds arch; a contract file takes arch at any tier; full takes all four.

- After review fixes, a delta of docs or at most 20 lines off risky paths carries the passes; a

- larger one is re-read by the one gate `wuwei evidence` names. When a repository's 28-day change

- failure rate is over 15 percent, every tier there rises one step and takes its full gate set.

- - A breaking change to an outward contract (declared with `!` or `BREAKING CHANGE:`, or found by the

- arch gate) has an `Announcement: <link>` line and the owner's `breaking:` confirmation at the head.

- - CI is green, every review thread is answered, a reviewer is requested, the owner reviewed changes

- under `owner_paths`, and the PR is not stale (three days or more open).

+ ## Done and deciding

- ## The doors

+ The plugin's `charters/_common.md` (`.claude/wuwei/charters/_common.md` when vendored) states once

+ what done means (Done) and how to decide and when to ask the owner (Decisions). Read it there;

+ this skill gives only the short form. Only safety gaps hold a merge (a test, the gates the diff

+ needs at the head, green CI, threads answered, owner review on `owner_paths`, a breaking change

+ confirmed, the spec at `full`). The rest is process fit: follow it, and the merge records any

+ misfit for the retro. Ask the owner only for a hard-to-undo choice you are unsure of, a change of

+ scope or goals, a trust question, an owner review or an exception, with the class first and your

+ recommendation. Never ask whether to continue planned work.

- WUWEI refuses: a merge with gaps; a PR opened ready, marked ready or given reviewers before its gates pass (a draft opens first); a force push, a push to or deletion of the default branch; admin

- merges, protection, status and access writes through `gh api`; a secret or the workspace canary in

- an outward call; writes to `.wuwei/ledger.jsonl`; a hand-made `wuwei hook` call; and a question to

- the owner that the process answers. Infrastructure commands ask the owner through the harness.

- Everything else passes and is recorded.

+ ## The PR body

- ## Deciding

+ The body keeps the repository's PR template sections and ends with the WUWEI footer, filled from

+ `wuwei --version` and `wuwei plan show <id>`:

+ `` <sub>[WUWEI <version>](https://taoq-ai.github.io/wuwei/) · Item `<id>` · <title> · Goal <G-n> · Tier <tier></sub> ``.

+ It holds a test or a `No test: <reason>` line, a `Size: <reason>` line over about 400 changed

+ lines, and a `Rollback: <how to undo>` line at `full` or on `owner_paths`. At `standard` and

+ `full`, when the repository has a spec engine, its artifacts are at the head. For spec-kit that is

+ `spec.md`, `plan.md` and `tasks.md` all checked; `full` adds `## Clarifications`, an `analysis.md`

+ with no open CRITICAL or HIGH, and checked checklists. For OpenSpec it is `proposal.md`, a

+ capability spec and `tasks.md` all checked.

- | | Sure | Unsure |

- |---|---|---|

- | Undone cheaply | act | act, record the assumption |

- | Hard to undo | act, with `Rollback:` | ask the owner |

+ ## The doors

- Ask with the class first (`one-way:`, `scope:`, `goal:`, `trust:`, `infra:`,

- `owner review: owner/repo#n at <sha7>`, `exception: owner/repo#n at <sha7>: <gap>`, `plan:`, `breaking: owner/repo#n at <sha7>: <what breaks>. Announced at <link>. Proceed?`) and your

- recommendation. Never ask whether to continue planned work.

+ WUWEI refuses: a merge with safety gaps; a PR opened ready, marked ready or given reviewers before

+ its gates pass (a draft opens first); a force push, a push to or deletion of the default branch;

+ admin merges, protection, status and access writes through `gh api`; a secret or the workspace

+ canary in an outward call; writes to the ledger (`.wuwei/ledger/`); a hand-made `wuwei hook` call;

+ and a question to the owner that the process answers. Infrastructure commands ask the owner through

+ the harness. Everything else passes and is recorded.

## Andon

A problem that breaks work for everyone in a repository: `wuwei andon owner/repo --reason "..."`.

New builds there wait; clear it with `wuwei andon owner/repo --clear` once fixed.