devbook

Delete every resolved annotation fence in a devbook chapter and nothing else, so a branch merges without carrying answered notes in its chapters and its diff. The last step of the annotation lifecycle: open means someone is waiting, resolved means answered and lives only the rest of the branch, gone is the resting state. Use when: clearing resolved notes before a pull request, tidying a chapter after a review, or when a chapter has answered comments still in it. Triggers on: "sweep the annotations", "clear resolved notes", "delete the answered comments", "resolved annotations are still in the chapter", "sweep before merging".

Implement an agreed devbook chapter the code does not yet satisfy: derive a change brief from it — outcomes, invariants, ubiquitous language, out of scope, acceptance checks, plus one change category (new functionality, change to existing behaviour, defect) — and hand that brief to the code-side flow that covers the category, the way capture-specs hands a chapter to the folder flow. Covers six kinds: an aggregate whole or a domain service in .devbook/domain/<context>/domain.md, a feature in features.md, a feature flag or setting in context.md, the building block view in arc42/, a component guideline in design/. Reads code first so the brief asks only for the delta; edits no source or test tree itself, and stops with the brief when no flow engine is installed. Use when: build the aggregate we agreed, implement this chapter, the chapter says X and the code does not, apply the spec. DO NOT USE FOR: writing a chapter from code (capture-specs), or checking drift without changing anything (verify-change).

Bring devbook into a repository for the first time — adopt the .devbook/arc42/.domain/.tech/.design/.ai devbook folders, scaffold one starting chapter per adopted folder, install the devbook-meta checker and its CI workflow, install its folder rules with a wrapper per host, write devbook's section of AGENTS.md, and write the stamp. Refused where components.devbook already exists: that repository is initialized, and devbook:update moves it forward. Use when: adopting devbook in a repository that has never had it. Triggers on: "devbook init", "init devbook", "install devbook", "set up devbook", "adopt the devbook folders", "scaffold arc42/", "scaffold domain/", "set up tech/", "set up design/", "track AI adoption".

Read every adopted devbook folder and report the prose that does not earn its lines — a hedge in a sentence stating a fact, a paragraph restating its heading, a closing summary repeating the body, a term defined a second time outside the ubiquitous language, a name in prose that no longer exists in the tree — beside what devbook:validate reports about structure. Writes nothing: the report is the output, and an edit is a person's, through the folder's flow. Use when: tightening chapters before a review, finding what a fold or rename left behind in prose, or on a cadence. Triggers on: "check the chapters' prose", "what is stale in the devbook", "tighten the chapters", "prose check", "devbook prose".

Refresh a repository technology graph from deterministic package inventories and repo analysis. Use when: update technology graph, refresh tech/, scan .NET packages, scan frontend packages, package graph, technology inventory. Produces inputs for the `tech/` flow and keeps package-derived facts reproducible through scripts.

Move a repository that already has devbook forward — refresh the devbook-meta checker, its CI workflow, the folder rules with a wrapper per host, and devbook's section of AGENTS.md, run outstanding schema migrations, create a folder adopted since or orphan one dropped, and re-stamp. One idempotent operation covering a plugin upgrade, a change in which folders are adopted, and migration-only. Refused where no components.devbook stamp exists: run devbook:init first. Use when: upgrading devbook, adding or dropping a devbook folder, or a migration is outstanding. Triggers on: "devbook update", "update devbook", "upgrade devbook", "devbook sync", "run devbook migrations", "adopt another devbook folder", "drop a devbook folder".

Validate a repository's devbook corpus without writing a generated file, and repair what it reports in the chapters — broken metadata references, malformed or missing meta blocks, fields the schema no longer defines, and stale _meta indexes. Asks about the chapters only, never about the installation: stamp drift and outstanding migrations are not this skill's question. Use when: the devbook-meta check fails, CI warns about drifted indexes, or references do not resolve. Triggers on: "devbook validate", "validate devbook folders", "devbook check", "devbook-meta failed", "broken reference", "stale _meta", "build.mjs --check".

Check a devbook chapter against the code that implements it and report the drift verdict — aligned, code-ahead, spec-ahead, conflict, or unresolved — per chapter, without writing a chapter or a brief. Covers the same six kinds as capture-specs and apply-change: aggregate, domain-service, feature, setting, building-block, design-component. Use when: is the chapter still true, did the code drift from the spec, does the implementation match what we agreed, spec code drift, check before a review or a pull request, which side moved. Reads source and unit tests only; runs nothing and changes nothing. DO NOT USE FOR: writing the chapter (capture-specs) or implementing the delta (apply-change) — it names which of those the verdict calls for.