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".

Check a repository against devbook without writing to it, and repair what it reports — broken metadata references, fields the schema no longer defines, missing meta blocks, outstanding migrations, stamp drift, a stale AGENTS.md section, and stale _meta indexes. The check-only half of devbook:install. Use when: the devbook-meta check fails, CI warns about drifted indexes, references do not resolve, or a migration may be outstanding. Triggers on: "devbook check", "devbook-meta failed", "broken reference", "stale _meta", "validate devbook folders", "build.mjs --check".

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.

From-spec direction (build), aggregate kind: turn an agreed but unbuilt aggregate — the root plus its owned entities, value objects, and enums, and the domain events it raises — into a change brief plus a change category, then stop.

From-spec direction (build), building-block kind: turn an agreed but unbuilt structure in .arc42/05-building-block-view.md into a change brief plus a change category, then stop.

From-spec direction (build), design-component kind: turn an agreed but unadopted component guideline in .design/component-libraries.md into a change brief plus a change category, then stop.

From-spec direction (build), domain-service kind: turn an agreed but unbuilt `type: domain-service` chapter in .domain/<context>/domain.md into a change brief plus a change category, then stop.

From-spec direction (build), feature kind: turn an agreed but unbuilt `type: feature` or `type: sub-feature` chapter in .domain/<context>/features.md into a change brief plus a change category, then stop.

Reconcile a repository with devbook — adopt the .arc42/.domain/.tech/.design/.ai devbook folders, install or refresh the devbook-meta generator and its CI checks, write devbook's section of AGENTS.md, run outstanding schema migrations, and write the stamp. One idempotent operation covering first install, plugin upgrade, a change in which folders are adopted, and migration-only. Use when: adopting devbook, upgrading it, adding or dropping a devbook folder, or a migration is outstanding. Triggers on: "devbook install", "install devbook", "devbook sync", "set up devbook", "adopt the devbook folders", "scaffold .arc42", "scaffold .domain", "set up .tech", "set up .design", "track AI adoption", "upgrade devbook", "run devbook migrations", "devbook-install".

To-spec direction (capture), aggregate kind: read an implemented aggregate whole — the root plus every entity, value object, and enum it owns, the shared value-object and enum groupings, and the domain events it raises — and write or refresh those chapters in .domain/<context>/domain.md. Use when: an aggregate exists in code but has no chapter, the chapter is a stub, sub-chapters are missing or stale, an event is raised with no chapter, the code has grown invariants the chapter never recorded, document the aggregate we built. Reads source and unit tests as evidence and routes the write through the `.domain` flow. DO NOT USE FOR: turning an agreed but unbuilt aggregate chapter into work (use from-spec-aggregate), or for the domain-service, feature, or bounded-context chapters around it (use the matching to-spec-* skill).

To-spec direction (capture), building-block kind: read the implemented module and component structure and write or refresh .arc42/05-building-block-view.md, with its decomposition levels, responsibilities, interfaces, and diagram. Use when: the building block view is missing or stale, projects were added or restructured, the decomposition diagram no longer matches the solution, document the structure we built. Reads source and project structure as evidence and routes the write through the `.arc42` flow. DO NOT USE FOR: turning an agreed but unbuilt building-block chapter into work (use from-spec-building-block), or for the deployment, bounded-context, or design-component chapters around it (use the matching to-spec-* skill).

To-spec direction (capture), design-component kind: read the component library and component usage actually in the code and write or refresh the component chapters in .design/component-libraries.md, with adoption, token usage, and known gaps. Use when: a component library is in use with no chapter, the recommendation is stale, components were hand-rolled around a gap, document the component adoption we have. Reads source and manifests as evidence, defers to the authoritative design source, and routes the write through the `.design` flow. DO NOT USE FOR: turning an agreed but unbuilt design-component chapter into work (use from-spec-design-component), or for the building-block, deployment, or feature chapters around it (use the matching to-spec-* skill).

To-spec direction (capture), domain-service kind: read an implemented domain service, policy, or process manager and write or refresh its `type: domain-service` chapter in .domain/<context>/domain.md, including invocation semantics. Use when: coordinating logic exists in code with no chapter, a policy or process manager is undocumented, the chapter omits which aggregates the service coordinates, document the domain services in this context. Reads source and tests as evidence and routes the write through the `.domain` flow. DO NOT USE FOR: turning an agreed but unbuilt domain-service chapter into work (use from-spec-domain-service), or for the aggregate, feature, or bounded-context chapters around it (use the matching to-spec-* skill).

To-spec direction (capture), feature kind: read a shipped capability and write or refresh its `type: feature` or `type: sub-feature` chapter in .domain/<context>/features.md, including feature-flag and depends-on. Use when: a capability ships but features.md does not list it, the feature breakdown is stale, a feature flag has no chapter, document the features we built, capture the feature by using it. Runs the application and captures screenshots of the flow as primary evidence, alongside source and tests, then routes the write through the `.domain` flow. DO NOT USE FOR: turning an agreed but unbuilt feature chapter into work (use from-spec-feature), or for the aggregate, domain-service, or bounded-context chapters around it (use the matching to-spec-* skill).