devbook-config

Check whether a repository's ai/ adoption record still describes the stack it actually has — which plugins are installed and enabled, which flows and schedules the copies on disk ship, and what the stack config wires — then hand every edit to flow-spec. Reports drift; never writes a chapter and never rates one. Use when: the adoption record has gone stale after an upgrade, a plugin was added or removed, or you are reviewing how this repository works with AI. Triggers on: "refresh the adoption record", "is my ai/ still accurate", "update .devbook/ai", "which plugins are missing from the adoption map", "does the ai folder match what is installed".

Answer a question about this marketplace and the plugins in it — what devbook, delivery, the bridges, the surfaces, and the fan-out lane are and how they fit together, which version of a plugin is installed against the newest one published, which plugins are enabled here, and how this repository has wired its flows, roles, gates, and policy. Reads only; it never installs or reconciles anything. Use when: asking how the stack works, comparing installed against newest, checking what is enabled, or reading a repository's flow wiring. Triggers on: "what is devbook", "explain the delivery engine", "how do the plugins fit together", "which version am I on", "is there a newer version", "which plugins are enabled", "how are my flows set up", "what does this repo bind", "which gates are on".

Diagnose a repository's installation of this marketplace without writing anything — every component's stamp against what is on disk, outstanding devbook migrations, a stale or customized AGENTS.md section, and each installed plugin against the newest published — and name the one skill that fixes each finding. Reads every stamp, which is why it lives here and not in any one component. Use when: something may be out of date, a migration may be outstanding, a stamp may have drifted, after an upgrade, or before trusting a repository nobody remembers configuring. Triggers on: "devbook-config doctor", "doctor", "is the stack healthy", "is my installation current", "outstanding migrations", "stamp drift", "is the AGENTS.md section stale".

Set a repository up for this marketplace for the first time — decide which installed plugins it will actually use, write .devbook/config.json with its id and, when the delivery engine is among them, the engine-owned keys (bindings, extensions, policy, gates), validate them against the schema, and then hand each adopted component its own init skill to materialize what it installs. Writes the engine keys only, never another component's stamp, and never sets up a plugin this machine has not installed. Refused where .devbook/config.json already exists: run devbook-config:update. Use when: adopting the stack in a repository, wiring flows for the first time, or creating the stack config. Triggers on: "devbook-config init", "init the stack", "set up the stack here", "adopt the delivery engine", "create the stack config", "create .devbook/config.json", "wire up my flows", "onboard this repo".

Say what is true of this machine and nobody else's — QA depth inside the repository's ceiling, the retry budget, a role or MCP binding that exists only here, an extra checkpoint of your own, the environment and model your scheduled routines run with, the model each flow category uses, and machine-only instructions — and write it where the stack reads it: the user layer of the stack-config overlay by default, the repository layer when an answer is about one repository, the model-selection file, and AGENTS.local.md — all under your devbook config directory, none inside the clone. Never the committed config. Use when: a first run would otherwise take the team's defaults without saying so, the report says no user overlay exists, or a personal setting should stop being re-asked. Triggers on: "devbook-config local", "set up my overlay", "what is true of my machine", "remember my QA depth", "stop asking for the environment", "set my model preferences", "create AGENTS.local.md".

Move a repository's whole configured stack forward in one run — refresh the catalog, report which installed plugins are behind, then fan out to every adopted component's own update skill so outstanding migrations run and stale files are re-materialized, and re-validate the engine-owned keys of .devbook/config.json and the overlays over it. Skips what this machine has not installed and what this checkout has not enabled, without ever dropping a stamp. Use when: upgrading the stack, a plugin is out of date, a migration is outstanding, or the config no longer validates after an upgrade. Triggers on: "update the stack", "upgrade the stack", "update everything", "am I on the latest", "update my plugins", "run outstanding migrations", "the config stopped validating", "the stack config is still in .github", "there is still a flow-context.md".