Knowledge and skills

The council knows nothing specific about your work until you tell it. Knowledge says what is true; skills say how you do things.

Knowledge packs

A pack is a markdown file with a short front matter: your vocabulary, your constraints, the things already decided. The council treats it as authoritative over the model's assumptions. The packs that match a request are inlined into it; the rest are listed so a member can go and read one.

Mark a pack --always to send it with every request.

Learning a repository

The quickest way to fill it is to let it read. Knowledge › Learn a repository surveys the codebase (languages, layout, the commands that matter, the conventions the git history follows) into a pack you can edit afterwards. Every line says which file it came from, and no .env is opened.

Skills

A skill is a markdown file that says how to do a thing your way: write a migration, review a pull request, model a threat. Ten ship, under The library in the sidebar. The skills that match a request are offered to the members; a tool-capable engine reads the whole file when it needs it.

Workflows

A workflow is a named sequence of steps, each with the member who takes it. Five ship: decide, panel, review, shape and ship. A run pauses for you between stages.

Three layers

Every pack, skill, member and workflow resolves through three layers, narrowest wins: what ships, your ~/.valhalla/, and a repository's own .valhalla/. A project can replace a built-in skill without forking anything, and a team shares a layer by committing it.