Kevin Veen-BirkenbachandClaude Opus 5.5
3c2f6c44b5
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>
2.5 KiB
2.5 KiB
name, description
| name | description |
|---|---|
| kvb-org-matrix | One matrix of everything in flight with confidence and break risk per item. Trigger on "status", "übersicht", "wo stehen wir". |
One-shot overview, no side effects: it reads state and reports it, never edits, stages, commits, deploys or starts work. The operator decides what to act on.
Collect the state
In parallel; skip a source the session lacks, and never invent a row for one you could not read:
- Tasks: the
kvb-org-rasciregister first, then the session's todo list, the operator's goals this session, and the requirement or plan documents the work follows. - Peers:
council.py listandnews.py show --all(thekvb-org-organizeskill's scripts); never message a peer for status. - Working tree:
git status --shortandgit log --oneline -10: uncommitted and untracked files are open work, commits since the branch point closed work. - Running: background jobs, spawned agents not yet reported, scheduled
/loopwake-ups, remote runs (CI, deploys). Poll their live state; a job is not "running" because you started it. - Remote: open PRs and issues for the branch and their check conclusions, when a forge CLI is available.
The matrix
One table, most-blocking first, one row per item:
| Item | State | Conf. | Break risk | Evidence / next step |
- State:
open,running,blocked,done.donemeans verified (a passing run, a green check, a reproduction that now succeeds); work that merely looks finished isopen. - Conf. and Break risk: two separate percentages per the
kvb-check-confidenceskill, only for rows that changed something;-for pure observation rows. - Evidence / next step: for
donethe strongest proof line (what ran, what it returned), otherwise the single next action.
Then at most three lines:
- Blocked on: what needs the operator (a decision, a credential, an approval); omit when nothing does.
- Residuals: what keeps the lowest confidence below 100.
- Running: what reports back on its own, so the operator need not wait on it.
Rules
- Cover everything in scope, including work the operator did not ask about: a forgotten background job or an unpushed commit is what the matrix exists to surface.
- Report what the poll returned, never a predicted result; a running item has no confidence number yet.
- One row per item, no per-item paragraphs; the operator asks when a row needs explaining.