Skip to content

Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.

skills(audit-agents): the full run belongs to the end of a spec

David Zhangbf2785213c97
diff --git a/.agents/skills/audit-agents/SKILL.md b/.agents/skills/audit-agents/SKILL.md
index 77348f2..8b97ccb 100644
--- a/.agents/skills/audit-agents/SKILL.md
+++ b/.agents/skills/audit-agents/SKILL.md
@@ -25,7 +25,7 @@ AGENTS.md is read by everyone who will ever work on the project. Picture the nex
- **A thousand people.** A newcomer can act on it without knowing this session, this author or this month's work.
- **Changes what they do.** Delete a line a capable contributor already follows.
- **Plain and concrete.** A principle is not an abstraction. "Look at the picture" works; "match verification to the claim" doesn't. Prefer a short sentence with its consequence, and one example from the product over a general noun.
-- **Iteration speed.** This is the core principle and must be stated outright: optimize the time to feedback you can trust, run the narrowest check that answers the question, and run everything once, when the plan's implementation is finished. Flag any rule that adds process to every loop, puts the full run before a commit, merge, push or finished feature, or names checkpoints for it along the way. The full run comes earlier only when the next piece of work can't be trusted without it. Never trade away a real acceptance requirement for speed.
+- **Iteration speed.** This is the core principle and must be stated outright: optimize the time to feedback you can trust, run the narrowest check that answers the question, and run everything once, when the spec's implementation is finished. Flag any rule that adds process to every loop, puts the full run before a commit, merge, push or finished feature, or names checkpoints for it along the way. The full run comes earlier only when the next piece of work can't be trusted without it. Never trade away a real acceptance requirement for speed.
## Shape
diff --git a/.agents/skills/audit-agents/assets/example-agents.md b/.agents/skills/audit-agents/assets/example-agents.md
index b2211c2..ba3975d 100644
--- a/.agents/skills/audit-agents/assets/example-agents.md
+++ b/.agents/skills/audit-agents/assets/example-agents.md
@@ -18,7 +18,7 @@ Optimize for iteration speed. The measure is the time to feedback you can trust,
Run the narrowest check that answers your question: one test, then one file, then one package. That is the proof for everyday work, including a commit, a merge and a push.
-**Run everything once, when a plan's implementation is finished.** Running everything is slow and saturates the machine. Until then a change is checked by what it can move: its own tests and the output it touches. That is enough for a commit, a merge, a push and a finished feature. A failure that only the full run finds is fixed at the end; that is cheaper than gating every step.
+**Run everything once, when a spec's implementation is finished.** Running everything is slow and saturates the machine. Until then a change is checked by what it can move: its own tests and the output it touches. That is enough for a commit, a merge, a push and a finished feature. A failure that only the full run finds is fixed at the end; that is cheaper than gating every step.
A change that reaches the whole system does not bring that run forward on its own. While more work is coming, the full run still waits for the end. Run it sooner only when the next piece of work can't be trusted without it.