What problem does it solve? Technology radar chapters under tech/ drift out of sync with what the repository actually depends on, and nobody remembers to update them. This Skill runs the refresh on a schedule so drift between a package manifest and a chapter is detected and proposed automatically. ## Core Features & Use Cases - Scheduled tech-graph refresh: Invokes devbook:tech-update over every tech/ layer (or a single layer file) to compare package inventories against committed chapters. - Draft pull request landing: When chapters move, opens a draft PR titled chore(tech): technology graph refresh <YYYY-MM-DD> containing the inventory deltas and every chapter change. - Guardrails: Never marks technologies adopted, hold, or retired on its own, never commits temporary inventory JSON, and never regenerates _meta/ indexes owned by the daily validate schedule. - Use Case: A team wires the weekly tech-update trigger in their host scheduler; each week the run inventories dependencies, updates the tech/ chapters, and a person reviews and merges the resulting draft PR. ## Quick Start Run the scheduled tech-update over all tech layers and open a draft pull request with whatever changed.
