refactor(skills): cap every SKILL.md at 600 words and cut agent messages
Every loaded SKILL.md and every listed description is paid on every turn of every session, and every delivered message costs its recipient a full turn. scripts/budget.py gains SKILL_WORDS = 600, enforced by test_lock, and test_naming forbids a skill naming its own slash command; 53 descriptions and 10 body lines drop it. The 18 longest skills move details into 31 side files read only in their situation (organize's capacity, succession, peers, offices, relay and lineage; cleanup's docker, worktrees, execute and ask; code-tune, changelog, triage, dream, split and others), so all SKILL.md files shrink from 33866 to 26291 words without dropping a rule; an independent review of HEAD against the new text found no loss in 60 of 64 skills and three weakenings, now restored (WSJF re-estimates after an objective change, cleanup's volume checklist, essence's absolute dates). The kvb-org-organize Peer protocol sends status that asks nothing to the news board, answers nothing that asks nothing, keeps messages terse, and lets light runs admit themselves in the operator's wording; the skills follow it (operator reads the register, relax and wakeup reply through the news, evening collects them there, wsjf asks only for missing estimates, cleanup and triage batch their questions). Skills that explore code ask the codebase-memory-mcp graph first, subagent briefs scale with the stakes and cap their answers, and the skills that need the full register or council tables call show --wide or list --long. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
34b434a744
commit
3c2f6c44b5
99 files changed
+2110
-2086
No files matched your search
@@ -7,9 +7,8 @@ description: >
|
||||
---
|
||||
|
||||
Break risk is the probability the change breaks something it did not intend to
|
||||
touch. It is not the inverse of fix confidence, and it is not a mood. Derive it
|
||||
by the steps below; a number produced without them is a guess wearing a
|
||||
percent sign.
|
||||
touch: not the inverse of fix confidence, not a mood. Derive it by the steps
|
||||
below; without them a number is a guess.
|
||||
|
||||
## Fast path
|
||||
|
||||
@@ -22,7 +21,10 @@ under 1%, and skip the method. Any other file takes the full method.
|
||||
|
||||
1. **Consumers**: enumerate every consumer of everything the change alters, in
|
||||
the committed state (`git grep <symbol> HEAD`) and of its output; say the
|
||||
count. A caveat never licenses a low number; an enumeration does.
|
||||
count. A caveat never licenses a low number; an enumeration does. Query
|
||||
the codebase-memory-mcp graph first (`detect_changes`, `trace_path`,
|
||||
`search_graph`; the `kvb-agent-optimize` skill sets it up), grep and read
|
||||
after.
|
||||
2. **Delta**: run the old and the new code on today's inputs and compare at
|
||||
the surface where the difference shows (rendered output, emitted config,
|
||||
returned set, wire bytes), not as the source reads.
|
||||
@@ -45,7 +47,7 @@ its residuals. Anchor roughly:
|
||||
|
||||
- **Under 5%**: consumers enumerated, delta measured at the surface, every axis
|
||||
of the matrix covered by executed evidence, failure mode closed.
|
||||
- **5 to 15%**: measured, but one axis or one layer rests on reasoning — no live
|
||||
- **5 to 15%**: measured, but one axis or one layer rests on reasoning: no live
|
||||
run, a mode not exercised, a runtime the render cannot prove.
|
||||
- **15 to 40%**: a real behaviour change whose consumers are enumerated but
|
||||
whose effect is unmeasured, or a latent finding with a plausible trigger.
|
||||
|
||||
Reference in new issue
Block a user