Save a lesson for the team
Two kinds of lesson are worth keeping: the ones you decide (“we use pnpm here”) and the ones evaluations find (“the agent keeps skipping the integration tests”). Both end up in front of the next session
A decision, from your agent
Section titled “A decision, from your agent”Remember for the team that this repository uses pnpm and that any change under checkout/ needs the integration tests run. Make it relevant to this repository and visible to the whole organisationSay two things: where it applies (this repository, a project, the whole organisation) and who should see it (just you, a team, the organisation). The memory is saved, and the next session in this repository sees it in the memory index that kcap injects at session start
Later:
What do we already know about deploying this service?Update the pnpm memory: we moved to bun last weekA finding, from an evaluation
Section titled “A finding, from an evaluation”Evaluations retain their findings as facts. When the same lesson keeps turning up, kcap groups the facts into a draft document. A lead reviews it:
- Choose the repository in Scope and open Knowledge → Docs
- Open the draft. Read the Pending draft, compare it with the Serving version if there is one, and check the Members: the facts behind it, each with the sessions it was seen in
- Edit the wording, choose Approve as: Skill, and Approve
A skill is loaded by the agent when the task calls for it, which keeps session-start context small. Install it in the repository:
kcap skills syncThe agent now has kcap-<slug> beside its other skills, in every checkout where sync has run
A short rule, in the repository
Section titled “A short rule, in the repository”Some rules belong in version control, where a code review sees them. In Knowledge → Queue, promote the lesson with Write to CLAUDE.md / AGENTS.md, then:
kcap curate applyIt shows the diff and asks before writing a managed block into the instruction file