Install the dkitchen multi-agent workflow into this repo. Finds out what the repo and the user need, then walks through each build skill in turn. Run once per repo, or again to change the setup.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Setup Dkitchen?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/917dhj-setup-dkitchen)
---
name: setup-dkitchen
description: Install the dkitchen multi-agent workflow into this repo. Finds out what the repo and the user need, then walks through each build skill in turn. Run once per repo, or again to change the setup.
disable-model-invocation: true
---
# Set up dkitchen
Install the kitchen into the current repo. The user is the head chef: every rule you install exists to keep their attention on direction and decisions. This skill is the entry: it checks the prerequisites, settles the language and what the user needs, then walks through each build skill the user needs. Each build skill settles, drafts, and writes its own part. You verify and hand over at the end.
Shared install steps, such as prerequisites, language, rendering, and pointer blocks, are in [kitchen/README.md](../../kitchen/README.md#installing). Read it first.
## 1. Explore
Read the repo's starting state; assume nothing.
- **Prerequisites**: each one in [Installing](../../kitchen/README.md#installing).
- **Existing setup**: `AGENTS.md`, `CLAUDE.md`, `.claude/CLAUDE.md`, `docs/agents/`, `.dkitchen.toml`, `.claude/settings.json`. Note which build skills already ran: `docs/agents/roles.md` for `build-team`, `docs/agents/code.md` for `build-repo`, `docs/agents/runner.md` for `build-runner`, `docs/agents/unattended.md` for `build-night`.
- **The work**: the README, the main code, how tests run, whether scripts loop over items, and whether there are long jobs, several parallel workstreams, or a user who wants progress while away.
- **Language**: the language the user writes to you in, and the language of the repo's docs.
Done when you can name, with evidence, each prerequisite's state, which build skills already ran, and a recommendation for each need in step 3.
## 2. Present the findings
Summarize what is present and what is missing in a short list. Missing prerequisites come first, each with the command that fixes it. When Claude Code or Codex is unavailable, say plainly that this version of dkitchen needs both, and ask whether to stop or to install the rules anyway.
## 3. Settle the language and the needs
One question at a time. Lead each with your recommendation so the user can accept it in a word, and skip any that exploration already settled.
**Language.** Recommend the language the user writes to you in, and settle the vocabulary as [Installing](../../kitchen/README.md#installing) says. The build skills reuse this answer and do not ask again.
**Needs.** Ask each as a yes or no:
| Need | Recommend | Build skill |
| --- | --- | --- |
| A team of agents: roles, tickets, PR review | Always yes; every other part builds on it | [build-team](../build-team/SKILL.md) |
| Code the agents write and change | Yes for any repo with code the agents change; the reference checks need Python | [build-repo](../build-repo/SKILL.md) |
| Work done item by item: evaluations, batch inference, data processing | Yes when the repo has scripts that loop over items; needs `build-repo` | [build-runner](../build-runner/SKILL.md) |
| Work that keeps moving while the user is away | Yes when the repo has long jobs or several parallel workstreams, or the user asks for it | [build-night](../build-night/SKILL.md) |
Done when the language is settled and every need has an answer.
## 4. Build each part
Take the chosen build skills in the table's order: open each one's `SKILL.md` and follow it from its first step to its write step, carrying the settled language into it. A build skill already installed is updated in place. Finish one before starting the next, since each later skill builds on the earlier ones' files.
Done when every chosen build skill has written its approved draft.
## 5. Verify
Run the checks in [Installing](../../kitchen/README.md#installing), then each chosen build skill's own verify step. Fix what fails.
Done when every check passes, or the user has been told exactly which one fails and why.
## 6. Hand over
Give the user each build skill's hand-over points in one short list, in the table's order. End with: the rules are theirs to edit, and `/improve-kitchen`, run every couple of weeks, turns what keeps going wrong into checks, tools, or rules; each build skill can be run again on its own to change its part; and `/setup-dkitchen` runs the whole setup again.
