This is how you keep architecture docs honest and current without them becoming fantasy fiction. It runs in three modes: backfill writes the first doc for a module that's running but never documented, update syncs existing docs to match code changes, and check catches drift between designs and reality or between multiple architecture files. The hard rule is it only documents what exists in code right now, with file:line anchors for every claim. No roadmaps, no aspirational "we'll refactor to" statements. It explicitly won't let you write six docs at once or check everything in one pass because that's how details get sloppy. Worth running after each feature lands to keep your system map from rotting into historical fiction.
npx skills add https://github.com/liuzhengdongfortest/codestable --skill cs-arch