Five steps from nothing to a brigade working one of your issues. Nothing here
starts a worker, creates a label or uses a credential until you say so, and
kitchn never writes a file into your repository. Parts marked intended
output show how a step will look once its feature ships.
Not released yet: #18: install script, crate and the kitchn binary name.
02
Step 2: Put /kitchn in your agents
The /kitchn skill is how you talk to kitchn from inside a session. Install it once per agent you use.
Claude Code and CodexIntended output
kitchn skill install claude-code codexClaude Code: installed /kitchn in ~/.claude/skills/kitchnCodex: installed /kitchn in ~/.codex/skills/kitchnThe skill reads the house from the repository you open. It grants nothing.
It worked when
Type /kitchn in a new Claude Code or Codex session and the skill shows up.
Nothing changed in any repository.
Not released yet: #17: the /kitchn skill and its installer.
03
Step 3: Register your house
Install the agents you want to cook with, then run kitchn house init from a checkout. It asks only what it can't infer, shows the result, and registers your house.
Register the house
kitchn house initRegistry directory [~/.kitchn]:House name: acmeRepositories kitchn may work in [acme/app, from this checkout]:Where kitchn may post [acme/app, the repositories]:Found Claude Code and Codex on PATH. Who works each station? Sous-chef plans and splits work [Claude Code]: Station cook writes the code [Codex]: Expediter reviews at the pass [Claude Code]:No house-scoped GitHub access to read required checks (see --github-requester).Required checks: test, lintRequired reviewers [expediter]:{ "house": "acme", "repositories": ["acme/app"], "grants": [], … }Register house acme in ~/.kitchn? [y/N]: yRegistered house acme in ~/.kitchn and pinned the default guidance at ed7da17.No authority or workflows activated.Saved your answers as ~/.kitchn/houses/acme.json. Review it any time.
It worked when
Press Enter to take a default in brackets; only the house name and the required checks needed typing.
house init says the house is registered and nothing was activated.
Scripting it? Every question has a flag, such as --house acme --required-checks test,lint --yes. Prefer a file you review first? kitchn house init --registry ~/.kitchn --config house.json still works.
04
Step 4: Start in Orca
Create a worktree and pick its agent. Orca opens that agent in the new worktree: type /kitchn. The first time in a repository, the skill binds it to your house. kitchn writes nothing into the repository.
Orca: Create worktree
Project
app
Run on
Local Mac
Create from
origin/main
Agent
Codex
Your Codex sessionIntended output
/kitchnOrca worktree app-export, project github:acme/app.acme/app isn't bound to a house yet, and acme claims it. Bind it to acme?yes, interactive only for nowBound acme/app to house acme in the registry; the working tree is unchanged.Doctor: setup incomplete. House-scoped repository access: Unobserved.Ready. Hand me an issue, a pull request or an idea.
The same binding from a shell
kitchn house setup --registry ~/.kitchn --house acme --workflows noneBound acme/app to house acme in the registry; the working tree is unchanged.Doctor: setup incompleteHouse-scoped repository access: Unobserved.No workers, schedules, labels, or external actions were activated.git status --short(nothing: no kitchn file in the repository)
It worked when
The skill names the Orca worktree and the repository it resolved.
Setup says the working tree is unchanged, and git status agrees.
Doctor names each missing capability or access with its next step.
Starting a new repository instead? kitchn init app --house acme --repository acme/app --template <name> previews the house template before writing it.
Not released yet: #17: the /kitchn skill and its first-run setup, #93: house bindings outside the repository (PR #96).
05
Step 5: Run a real order
Write a short issue, let kitchn turn it into a spec, then hand it to the brigade and watch the pass.
Issue #72
Export orders as CSV
Shop owners want their orders in a spreadsheet. Add a CSV export
to the orders page, with the same filters as the list.
Refine it into a specIntended output
/kitchn issue refine #72Read the orders page, its filters and the last 20 merged PRs.Proposed spec with acceptance criteria and 3 sub-issues: #73 CSV writer for orders ready #74 Export endpoint with filters blocked by #73 #75 Export button on orders page blocked by #74One decision needs you: should the export include cancelled orders?no, only active onesPosted the spec, 3 sub-issues and 2 blocked-by links after your approval.
Work itIntended output
/kitchn work #72House acme. #73 is ready; #74 and #75 wait on it.Start a cook on #73 now, and the rest as their blockers merge?yesOrca: worktree for #73, Codex cooking, Claude Code at the pass.10:14 Expediter sent #73 back: no test for an empty order list.10:31 #73 passes at exact head 9c41e0a. Waiting for your sign-off.10:33 You merged #73. Started #74.You stay the chef-owner. Merges wait for your sign-off.
Later: let it run on its ownIntended output
/kitchn schedule pickup every 15 minutesOrca automation: kitchn pickup on acme/app, every 15 min, Codex cooks.Doctor: every capability scheduled pickup needs is observed.Create this automation in Orca?create itCreated. It picks up issues labeled agent-ready; you still sign off merges.
It worked when
The issue now has a spec, sub-issues, and blocked-by links you approved.
Orca shows one worktree per ready sub-issue, and blocked ones wait.
Each PR reaches you only after the expediter passes it at its exact head.
A scheduled run is created only after you approve it, and only when doctor has observed every capability it needs.
Not released yet: #17: /kitchn issue refine and /kitchn work, #8: scheduled pickup.
