Kevin Veen-BirkenbachandClaude Opus 5.5
35dc37641d
rasci.py keeps the organisation's tasks in <council root>/rasci.json: RASCI roles, objective with key results, priority, worker, start, end, workdir, branch, tools and artifacts; done is refused while a key result is open. council.py writes every claim, takeover and release through, and show lists the live claims as one row per task with R, A, S, C and I columns. kvb-org-artefacts manages the artifacts in the same table for kvb-cleanup. The org, plan, triage, tune, cleanup, branch-gc and dream skills now record into and read from the register; five descriptions were tightened to keep the listing budget. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.7 KiB
2.7 KiB
name, description
| name | description |
|---|---|
| kvb-org-matrix | Print one matrix of everything in flight: tasks, workflows, background jobs, with confidence and break risk per item. Trigger on /kvb-org-matrix, "status", "übersicht", "wo stehen wir", or what is done, left or running. |
One-shot overview, no side effects: this skill reads state and reports it. It never edits files, stages, commits, deploys, or starts work — the operator decides what to act on after reading the matrix.
Collect the state
Gather in parallel, skip any source the session does not have, and never invent a row for a source you could not read:
- Tasks — the
kvb-org-rasciregister first, then the session's todo list, the operator's stated goals this session, and any requirement or plan documents the work follows. - Working tree —
git status --shortandgit log --oneline -10: uncommitted files are open work, commits since the branch point are closed work. Untracked files count as open. - Running — background bash jobs, spawned agents not yet reported,
scheduled
/loopwake-ups, and remote runs (CI, deploys). Poll their live state; a job you started 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 — probability the item does what it claims, and probability it breaks something else. Only for rows that changed something;—for pure observation rows. - Evidence / next step: for
done, the strongest proof line (what ran, what it returned). For everything else, the single next action.
Then at most three lines below the table:
- Blocked on: what needs the operator (a decision, a credential, an approval) — omit when nothing does.
- Residuals: what keeps the lowest confidence number below 100.
- Running: what will report back on its own, so the operator does not wait on it manually.
Rules
- Cover everything in scope, including work the operator did not ask about — a forgotten background job or an unpushed commit is exactly what the matrix exists to surface.
- Report what the poll returned, never a predicted result for work still in flight; a running item has no confidence number yet.
- Compress: one row per item, no per-item paragraphs. If a row needs explaining, the operator will ask.